Issue Feature Closed

#51088Improve Frontend error handling

Alexander Stehlik 08/15/13, 14:46 updated 08/27/13, 01:22

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?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.