-
Notifications
You must be signed in to change notification settings - Fork 37
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
Map application to 18f.gov. #219
Conversation
Since all CF requests are now redirected to HTTPS, we need to use a URL that handles SSL. This patch maps the Tock app to tock-app.18f.gov; the "-app" suffix is used to distinguish the route used by nginx (tock.18f.gov) from the route used by the app.
Map application to 18f.gov.
@jmcarp @RAMIREZG So, @NoahKunin and I both experienced visiting Visiting https://tock-app.18f.gov/ directly also gives a 403. |
@konklone: Tock is deployed to Cloud Foundry but accessed through the auth proxy that lives in the Hub. Previously, the Hub nginx server was proxying requests to Tock can't be accessed via Cloud Foundry directly (unless the user is already authenticated), since authentication happens via the auth proxy, so a 403 when hitting the CF deployment directly is the expected behavior. But getting a redirect to tock-app is a bug. Will take a look. cc @RAMIREZG |
Resolved. Hub PR coming soon; will link to this PR. |
Fix Tock proxy issue discussed in 18F/tock#219
Got it! Thank you for the explanation, and to @mbland for the fix.
Yikes -- I'm glad we fixed that, bumpy as it was. |
Since all CF requests are now redirected to HTTPS, we need to use a URL
that handles SSL. This patch maps the Tock app to tock-app.18f.gov; the
"-app" suffix is used to distinguish the route used by nginx
(tock.18f.gov) from the route used by the app.
Ping @RAMIREZG. We'll also need to update the staging app to live at tock-app-staging.18f.gov. See 18F/hub#358 for full configuration.