Project

General

Profile

Actions

Bug #54508

closed

Http Redirect 301 prevents browsers from retrieving the correct url after authentication

Added by Andreas Schosser over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2013-12-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hello TYPO3 Core Team

I had an issue with user restricted pages concerning the http status code of the redirect.

The Server sends status 301 and redirects to the configured login page. Status 301 indicates, that the browser may cache the redirect result and may never fetch the original url. So even when correctly authenticated and authorised the user cannot view the page unless he clears the browser cache.
It would be better to use status code 302 in this case, so the browser will try to fetch the original url.

I tracked the issue to file typo3/sysext/cms/tslib/class.tslib_fe.php, line 2788. I changed the status code manually from 301 to 302 ($redirectStatus = t3lib_utility_Http::HTTP_STATUS_302;).

Could you please change the status code or provide the possibility to configure it via typoscript.

Thank you,
Andreas


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #56423: Page shortcuts redirect with HTTP Status 301 and get cached on some devicesClosed2014-02-28

Actions
Actions

Also available in: Atom PDF