Task #89563
closedAdd redirect types
0%
Description
Compared to the extension yoast premium, there are still two types of HTTP missing:
410 Content deleted
451 Unavilable for legal reasons
Updated by Benni Mack almost 5 years ago
- Status changed from New to Needs Feedback
Technically this isn't a redirect anymore then, right?
Updated by Guido Schmechel almost 5 years ago
Maybe Richard can say a little bit about these http types?
Updated by Richard Haeser almost 5 years ago
On https://yoast.com/which-redirect/ you can see the reasons for those two status codes.
I think the 410 should be used more often. See https://yoast.com/deleting-pages-from-your-site/ for more information about that.
The 451 is not used that much but can still be of value.
Updated by Richard Haeser over 4 years ago
- Status changed from Needs Feedback to New
- Assignee deleted (
Richard Haeser)
Updated by Richard Haeser over 4 years ago
But indeed Benni, the 410 and 451 are technically no redirects and no target is necessary as well. Having those options might still be a good idea though.
Updated by Bastian Stargazer over 4 years ago
I upvote this feature request! After a huge website update I using the Redirect module to map the old page-structure to the new one.
But often not all old URLs having corresponding new ones. Currently I'm using a 301 (Moved Permanent) to redirect the old URL to the index-page, just to avoid a 404 not-found.
I thought about using the 303 (See other) for it, but not sure how Google respond to this.
After searching around for a while I also saw articles saying that 410 is good practice for this case.
Updated by Guido Schmechel over 4 years ago
I tried the subject. Extending the TCA is the least of the problems.
The status code > 400 is not accepted. The trigger seems to be $headers['location'] in file \typo3\sysext\core\Classes\Http\RedirectResponse.php. If I comment out this line, the HTTP code also applies. Otherwise 302 is taken.
I'm running out of ideas here, but maybe someone may need the information.
Updated by Gianluigi Martino over 4 years ago
For me it also doesn't work if i comment out "$headers['location'] in file \typo3\sysext\core\Classes\Http\RedirectResponse.php"
Created a Middleware and using "new RedirectResponse", but if i try to redirect with 410 or 404, it always redirect with the 302 statuscode (as mentioned by Guido Schmechel).
Have somebody a solution to resolve this problme?
Updated by Guido Schmechel over 3 years ago
- Related to Feature #93882: [FEATURE]: Allow "Redirects" with Status Code 410 for deleted files and Pages added
Updated by Georg Ringer about 1 month ago
- Status changed from New to Closed
problem is that the location header switches it to a 302.
as the 410 is no redirect I hacked together a solution for that usecase https://github.com/georgringer/error_redirects but I am closing this here as it is not a redirect.
maybe once the ext gets integrated in core but there is a solution now