Feature #51088

Improve Frontend error handling

Added by Alexander Stehlik over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
Start date:
2013-08-15
Due date:
% Done:

0%

PHP Version:
5.4
Tags:
Complexity:
medium
Sprint Focus:

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?


Related issues

Duplicates TYPO3 Core - Bug #23178: Wrong HTTP headers sent when trying to access pages that require login Closed 2010-07-14

History

#1 Updated by Philipp Gampe over 6 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.

#2 Updated by Alexander Stehlik about 6 years ago

I just found that a similar issue was already reported: #23178

Please mark as duplicate.

#3 Updated by Nicole Cordes about 6 years ago

  • Status changed from New to Closed

Closed because of duplication.

Also available in: Atom PDF