-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/docs leads to 404 #356
Comments
I think this is only partly fixed. The question mark icon leads to: https://batch.openaddresses.io/docs This redirects to http://batch.openaddresses.io:5000/docs/ which then fails to load. On the other hand https://batch.openaddresses.io/docs/ works as expected. So either the question mark link needs to be updated, or the redirect from |
I'm afraid I can't reproduce this? Can you try clearing your cache? This looks like the behavior I fixed. I've tried all the permutations and am seeing it correctly direct to the Swagger Docs. |
Something about generating the https://batch.openaddresses.io/docs/ page content is taking a very long time. I intermittently get 503s, blank pages after ~50 seconds, and the actual content you shared in the screenshot above. Also, I see the URL without the slash at the end redirecting to :5000:
|
Describe the bug
The docs link leads to a 404: https://batch.openaddresses.io/docs
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected a docs page.
Screenshots
Desktop (please complete the following information):
Additional context
This was previously filed in a different repo (openaddresses/openaddresses#6669), opening here since this is more applicable.
From my investigation I found that the nginx config specifies that the link should be
/docs/
batch/api/nginx.conf
Line 19 in 4af5207
And if we go to the route (https://batch.openaddresses.io/docs/) we see a different 404 page, which indicates the nginx filter gets hit:
But I also see that there's a route to
/docs
, without the slash.batch/api/index.js
Line 141 in 4af5207
My guess is that the nginx override is messing with the proper path.
Also, I'm thinking this broke with 1967934, which switched to Swagger. cc @ingalls
The text was updated successfully, but these errors were encountered: