TYPO3 Core

Maybe Richard can say a little bit about these http types?

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.

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.

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.

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.

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?