Ticket #305 (defect)
Opened 3 years ago
Last modified 3 years ago
produce an error if a custom error page file can not be opened
Status: closed (fixed)
| Reported by: | mikerobi | Assigned to: | mikerobi |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.1-rc2 |
| Component: | CherryPy code | Keywords: | |
| Cc: |
A custom file can be configured errorPage.xxx = "FileName".
If the file can not be opened then a default page is used, but it should send an error. But what kind of error should it seend
"This is supposed to be a 404 error but something also went wrong inside the server :)"
Change History
09/15/05 11:49:27: Modified by fumanchu
09/15/05 16:56:03: Modified by mikerobi
Even this would be an internal error i think it is more important for the response to have the intended status code.
09/15/05 17:19:14: Modified by fumanchu
{{{it is more important for the response to have the intended status code.} Understandable, but it has two major problems:
1. Different status codes have different requirements about what is legal (and desirable) in the headers and body, which a generic handler can't reproduce (without repeating ourselves massively in code, essentially rewriting CP again inside the error handler).
2. Nobody would ever be notified that a serious error occurred in the error page. But as a deployer/sysadmin, you need to fix the error-handler first: http://www.nedbatchelder.com/text/fix-err-hand.html
09/28/05 19:07:54: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
Implemented in [692].
500