Project

General

Profile

Actions

Bug #23178

closed

Wrong HTTP headers sent when trying to access pages that require login

Added by Ingo Renner over 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2010-07-14
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
On Location Sprint

Description

When trying to access a login protected page while not being logged in it may happen that a wrong header is sent.
The install tool allows to set a header for the page not found handling: [FE][pageNotFound_handling_statheader]
The default value for this setting is "HTTP/1.0 404 Not Found"
In a case where access is denied because the user is not logged in, this is the wrong header of course, it should be 401 instead.

Proposed solution: In case where access is denied because of missing privileges, TYPO3 should ignore the mentioned setting and send a 401 instead.

(issue imported from #M15114)


Files

15114.diff (957 Bytes) 15114.diff Administrator Admin, 2010-07-15 15:57

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #16472: Non accessible Page And PageNotFound Handler.ClosedAlexander Opitz2006-08-15

Actions
Related to TYPO3 Core - Bug #58728: Regression: unaccessible protected section with shortcut in rootlineClosed2014-05-12

Actions
Related to TYPO3 Core - Bug #86346: Hidden pages sent 403 HeaderClosed2018-09-21

Actions
Has duplicate TYPO3 Core - Feature #51088: Improve Frontend error handlingClosed2013-08-15

Actions
Actions

Also available in: Atom PDF