Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
openapi_url incorrect from behind reverse proxy
See original GitHub issueThe 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
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Even newer link 😄: https://fastapi.tiangolo.com/advanced/behind-a-proxy/
For anyone coming across this, the new link for the tutorial is here: https://fastapi.tiangolo.com/advanced/sub-applications-proxy/