Feature #15322
closed50x and 404 error handling to GUI web server configuration
100%
Description
If there is a PHP error early enough in the output of a page it ends up returning a 500 error with a blank page. We should handle this better if possible.
The ideal case would redirect to the crash reporter but if PHP itself has a problem that could end up in a loop or similar bad scenario. It seems like the best path is to return a static page that contains a link to the crash reporter along with some other helpful information. It wouldn't need to be much, could be similar to the login screen, a page with the logo and a short message explaining there was a problem.
Adding a 50x error page to the nginx config is easy but we may also have to change fastcgi error interception.
This isn't a blocker but nice to have, can be moved forward if there is no time.
If it's easy enough, once we have a basic appropriate static page we could use it for 404 errors as well.
Updated by Jim Pingle 9 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 6667cd717f7f5c038b1a439f322c71ef2427fa2d.
Updated by Jim Pingle 9 months ago
- Tracker changed from Todo to Feature
- Subject changed from Add 500 error handling to GUI web server configuration to 50x and 404 error handling to GUI web server configuration
- Description updated (diff)
- Private changed from Yes to No
Updated by Jim Pingle 9 months ago
- Status changed from Feedback to Resolved
Appears to be working as expected.