Project

General

Profile

Actions

Feature #84481

closed

add missing "HTTP/1.1 308 Permanent Redirect" constant to HttpUtility

Added by Stephan Jorek over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-03-19
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

In \TYPO3\CMS\Core\Utility\HttpUtility there are various HTTP status-headers defined as class-constants. This includes those for HTTP-redirects. I'm missing the "HTTP/1.1 308 Permanent Redirect" header here. Therefore I'll prepare a PR for TYPO3.CMS' master-branch to include this header as a class constant in the class mentioned above.

Research Information

The main difference to the well known “HTTP/1.1 301 Moved Permanently” header is, that 308 forces the client (aka Browser) to follow the redirect using the same protocol as the initial request. So for example with 308 a GET request must be followed with a GET request and a POST request must be followed with a POST request to the new location. With 301 status a POST request will be followed using a GET request to the new location.

The permanent redirect is defined here: According to Mozilla's research (as well as my biased experience) it is supported by all browsers. A compact and profound description of the HTTP redirect-related headers, can be found on Stackoverflow.

My Conclusion

Adding this header to the utility will not harm existing installations or anything at al.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Task #84626: Streamline HTTP Response codesClosed2018-04-05

Actions
Related to TYPO3 Core - Bug #94922: Missing HTTP status 308 for redirectsClosedMathias Brodala2021-08-18

Actions
Actions

Also available in: Atom PDF