Skip to content
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

Merged
merged 1 commit into from
Jul 30, 2015
Merged

Map application to 18f.gov. #219

merged 1 commit into from
Jul 30, 2015

Conversation

jmcarp
Copy link
Contributor

@jmcarp jmcarp commented Jul 30, 2015

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.

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.
geramirez pushed a commit that referenced this pull request Jul 30, 2015
Map application to 18f.gov.
@geramirez geramirez merged commit 157b81d into 18F:master Jul 30, 2015
@geramirez
Copy link
Contributor

@jmcarp https://tock-staging.18f.gov/ is up.

@konklone
Copy link

konklone commented Aug 3, 2015

@jmcarp @RAMIREZG So, https://tock.18f.gov is what most people have been using for long while (not the old cf.18f.us URL), and already had HTTPS configured properly.

@NoahKunin and I both experienced visiting tock.18f.gov, submitting our time cards, and having it get redirected to a 403 Forbidden error at https://tock-app.18f.gov. The time card did successfully get saved, so the redirect occurs after a successful operation.

Visiting https://tock-app.18f.gov/ directly also gives a 403.

@jmcarp
Copy link
Contributor Author

jmcarp commented Aug 3, 2015

@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 http://tock.cf.18f.us, which stopped working last week when we started redirecting to HTTPS for all CF apps. This patch deploys the internal Tock app to a URL at 18f.gov to get HTTPS, but we can't use tock.18f.gov, since that's already in use in the Hub config.

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

@mbland
Copy link

mbland commented Aug 3, 2015

Resolved. Hub PR coming soon; will link to this PR.

mbland pushed a commit to 18F/hub that referenced this pull request Aug 3, 2015
mbland added a commit to 18F/hub that referenced this pull request Aug 3, 2015
@konklone
Copy link

konklone commented Aug 3, 2015

Got it! Thank you for the explanation, and to @mbland for the fix.

Previously, the Hub nginx server was proxying requests to http://tock.cf.18f.us, which stopped working last week when we started redirecting to HTTPS for all CF apps.

Yikes -- I'm glad we fixed that, bumpy as it was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants