Feature #51088
closed
Improve Frontend error handling
0%
Description
I just realized that the error handling in the Frontend is not consistent.
For example when the access to a page is forbidden with the fe_group field, a 404 error is thrown when you try to access the page directly.
When you access a subpage of a forbidden page (access is prevented by the "Extend to subpages" checkbox in the page properties) a 503 (Service Temporarily Unavailable) error is thrown.
In my opinion at least the same error should be thrown in both cases.
An in this special case it should neither be a 404 nor a 503 but a 403 (Forbidden) error.
Are there already any plans to optimize the error handling in the Frontend? Or is this behavior intended?
Updated by Philipp Gampe over 11 years ago
AFAIK it is hard to change this without breaking older websites.
You can always use a custom pageNotFoundHandler to create your own behavior.
Maybe you should create a new thread on the dev list and just ask what others thing about this.
Updated by Alexander Stehlik about 11 years ago
I just found that a similar issue was already reported: #23178
Please mark as duplicate.
Updated by Nicole Cordes about 11 years ago
- Status changed from New to Closed
Closed because of duplication.