openapi_url incorrect from behind reverse proxy

[baodrate]

The use case:

I'm running FastAPI behind a nginx reverse proxy, at the path http://localhost/api/. The documentation front ends (swagger and redoc) are expecting openapi.json at http://localhost/openapi.json but it's actually routed at http://localhost/api/openapi.json.

Setting openapi_url to /api/openapi.json also changes the openapi.json path, so now it's looking for (through the proxy) http://localhost/api/api/openapi.json.

Ideally, it'd be great if we could specify the "public path" for the api. That's how e.g. vue does it

[tiangolo]

Thanks for the report. I'll check it, I agree that this is probably the most straightforward way to solve it, with a "public path".

This is also (probably) related to #8

I'll check it.

[baodrate]

Yup, sorry, I didn't notice #8. This is indeed a duplicate of that issue. Would you like me to close this one?

[tiangolo]

This should be solved by PR #26 by @kabirkhan . It is released as 0.4.0, the new docs are here: https://fastapi.tiangolo.com/tutorial/sub-applications-proxy/ 🎉 🚀

Let me know if it works for you.

[baodrate]

Love it! I'll test it out asap!

[tiangolo]

Great! Thanks for reporting back and closing the issue.

[RmStorm]

This should be solved by PR #26 by @kabirkhan . It is released as 0.4.0, the new docs are here: https://fastapi.tiangolo.com/tutorial/sub-applications-proxy/ tada rocket

Let me know if it works for you.

For anyone coming across this, the new link for the tutorial is here:
https://fastapi.tiangolo.com/advanced/sub-applications-proxy/

[Fogapod]

Even newer link 😄: https://fastapi.tiangolo.com/advanced/behind-a-proxy/