-
Notifications
You must be signed in to change notification settings - Fork 13
/current redirects to the prod app #364
Comments
@rhoughfec and I took a look at the issues referenced above plus the code that Lindsay posted in the issue, and this will most likely require the assistance of a back-end person. |
Documentation on cf routes:
Basically, we will want to change the route so regulations don't use the proxy. This simplifies things architecturally and will get the redirects for /latest working correctly. (Once we have fewer redirects in use we can do the same thing for the cms as well and just handle the redirects in wagtail. We will still need the proxy for s3 bucket naming.) The routes need to be changed from :
Change route to:
Go ahead and update the architecture diagram so that it is clear that eregs doesn't use the proxy after this is done. |
Is this issue being addressed already as part of the work you are doing now, @pkfec ? |
rerouting the eregs app to proxy is already taken care of. we can close this issue. |
This is an infrastructure task
I think the regulations site is creating redirects for /current but this is happening in the app and it is pointing to the app and not the proxied address.
We don't need redirects for eregs, so we might want to handle this with cloud.gov's built in stuff and not pother with the proxy. Or we can look at changing the regulations-site parser.
I think this is the code giving us an issue:
https://github.com/eregs/regulations-site/blob/d9223d07d92e54926c5bbcffee1690581d715d83/regulations/urls.py#L87
The text was updated successfully, but these errors were encountered: