-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add better error pages #119
Comments
PR #130 includes 404 handlers for teams and attacks. I wasn't sure what situations might cause 401s, 403s, or other 404s so I chose not to add Flask app wide handlers since they wouldn't have any helpful information in them. Are there cases where these other errors occur? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In many cases, when a 401, 403, or 404 should be presented, a non-formatted and not-very-helpful error page is shown.
For example, here's an attack that doesn't exist:
These should be formatted nicely, and contain helpful text where possible. Using
get_or_404
may get us a lot of the way there, in combination with a nice 404 page.The text was updated successfully, but these errors were encountered: