Merge lp:~gz/python-oops-tools/error_templates into lp:python-oops-tools
Proposed by
Martin Packman
Status: | Merged |
---|---|
Approved by: | Martin Packman |
Approved revision: | 35 |
Merged at revision: | 35 |
Proposed branch: | lp:~gz/python-oops-tools/error_templates |
Merge into: | lp:python-oops-tools |
Diff against target: |
38 lines (+24/-0) 3 files modified
src/oopstools/oops/templates/404.html (+5/-0) src/oopstools/oops/templates/500.html (+5/-0) src/oopstools/oops/templates/error.html (+14/-0) |
To merge this branch: | bzr merge lp:~gz/python-oops-tools/error_templates |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Benji York (community) | code | Approve | |
Review via email: mp+116031@code.launchpad.net |
Commit message
Show an error page rather than creating an oops for unknown locations
Description of the change
Currently going to <https:/
This branch adds trivial templates for the default 404 and 500 handlers so a client gets a (semi) meaningful response rather than a knock-on failure.
To post a comment you must log in.
This seems fine for what it is. I am curious why the 404 and 500 views
built into django were not being used.
Since these added views aren't all that fancy I would think the defaults
would work fine, if we knew how to activate them.