-
Notifications
You must be signed in to change notification settings - Fork 13
404 instead of 500s for bad calls in eRegs #385
Comments
I caught up with @LindsayYoung and what we're after here is updating the URL resolution (routing) to go through the e-regs application itself instead of the proxy app/router right now. What this means is making sure the e-regs application has the routes setup to handle these URLs if it doesn't already, and possibly updating some view logic to make use of Django's |
These 500 errors may also be related to eregs/regulations-site#485 - I'm seeing a lot of these in the logs recently. |
This issue will need to be fixed in https://github.com/eregs/regulations-site, not here. |
Seeing as how this is something that has to be done in the core eregs platform, all we should have to do once this is addressed is update the dependency for |
Unfortunately there is no one staffed to |
Specifically, the fix here will be just to update the module once the fix is made in https://github.com/eregs/regulations-site - for details on the fix, please see the ticket associated with it: eregs/regulations-site#485 |
- Addresses issue eregs#485: Missing data leads to an explosion - Also addresses FEC issue: fecgov/fec-eregs#385 - Throw a 404 error when navigating to a regulation that doesn't exist - Previously, the `utils.regulation_meta` function was returning `{}`, so accessing the 'meta' data was resulting in a 500 error
Update: The PR to eregs (eregs/regulations-site#515) was merged. Once there's a new release, we need to update our |
- New version 8.4.2 now throws 404 errors instead of 500 errors for missing regulations (eregs/regulations-site#515) - This will address fec-eregs #385: 404 instead of 500 for missing regulations
- New version 8.4.2 now throws 404 errors instead of 500 errors for missing regulations (eregs/regulations-site#515) - This will address fec-eregs #385: 404 instead of 500 for missing regulations
Addressed by #405 |
This came up in scanning. I think there should be a way add some resolve or 404 logic with django
The text was updated successfully, but these errors were encountered: