-
Notifications
You must be signed in to change notification settings - Fork 4
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
HTTPRedirect results in 503 in dev builds #29
Comments
Think this is the same as magfest/ubersystem#1377 |
Hm, that's interesting. The issues deal with different architectures/situations (vagrant vs Docker), so we'll keep both open, but if we end up fixing one we should see if it fixes the other. |
did a bunch of homework and the solution will be the same as what we're doing in magfest/ubersystem#1377, it would just need to be added to AC's docker setup. |
Nice! Awesome work. |
to fix in RAMS, just implement the same nginx +cherrypy config settings as magfest-archive/ubersystem-puppet#113 |
Any time the app uses a CherryPy
HTTPRedirect
call, the URL it returns ishttp
and the user sees a "503 Service Temporarily Unavailable" error. They must then manually change the URL back fromhttp
tohttps
. As a developer, this increases the time (and frustration) required for doing basic testing.I looked into this a bit, and it seems that this is a problem because we're using a reverse proxy. Nginx does not tell CherryPy what protocol to use, so CherryPy thinks that
http
is the correct URL type to return and nginx is not catching that and fixing it. There does seem to be a fix in CherryPy, but I have not yet made any more progress on it.As noted in the title, this is not a problem when you deploy using docker-staging or docker-production.
The text was updated successfully, but these errors were encountered: