You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a user access a resource that isn't found (not authorized, missing, whatever), they should land on an actual missing page that displays a generic "not found" error message whose status code is 404. No flashed message should be displayed.
Why?
We have some non-standard code that has already led me to confusion as to why abort(404) (a typical pattern) wasn't working as expected.
Also, this will make it possible for tests to check that a missing/unauthorized entity actually returns 404 (a clear sign of missing) instead of redirects to / and then doesn't have some heading (User 123) present in the response body.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a user access a resource that isn't found (not authorized, missing, whatever), they should land on an actual missing page that displays a generic "not found" error message whose status code is 404. No flashed message should be displayed.
Why?
We have some non-standard code that has already led me to confusion as to why
abort(404)
(a typical pattern) wasn't working as expected.Affected endpoint:
hushline/hushline/routes.py
Lines 553 to 562 in 4552cb0
Affected error handler:
hushline/hushline/__init__.py
Lines 95 to 98 in 4552cb0
Also, this will make it possible for tests to check that a missing/unauthorized entity actually returns 404 (a clear sign of missing) instead of redirects to
/
and then doesn't have some heading (User 123
) present in the response body.The text was updated successfully, but these errors were encountered: