TYPO3 Core

Hmm. That's also an interesting idea with the placeholder pages. But I'm not really sure if I think this is a good solution.

This might make the pagetree very messy and would produce a lot of pages without any content, which also don't behave like pages at all. They are not shown in any menus and behave more like folders than anything else. So I think they should also not be shown in the pagetree or at least have to option to hide them by clicking a checkbox. Which means a new feature for the pagetree aswell.

I checked the middlewares, that are called and the site-resolver gets called before the redirect handler. So here is my proposal for this ticket:

1. Add a new option "410 Gone" to the error code dropdown for redirects
2. Extend the redirect handler to check if we currently have a siteconfig with a configured 410 handler.
3. If this is the case and we are currently on a url which has an associated 410 Redirect, call the 410 handler from the site configuration and let it handle the error.
   If this is not the case return the error code 410 and cancel the request.
4. Optional Add possibility to automatically add a 410 redirect for pages, when they get deleted, like we do for renamed pages already.

This also has the advantage, that we can define files as "Gone" and also use regex for a whole bunch of pages without having to add dozens of placeholder pages.

I agree here: Let's focus on 404, and have custom extensions work with 410 if they need it. I don't think we should support 410 out of the box, as it is really an edge case, rather than an "editor feature" - editors are already have a hard time understand between 301 vs. 307.

If google and others change their 410 strategy we can re-open the ticket or create a new one.