TYPO3 Core

I would not recommend this, at least not without it being a conscious decision and opt-in. Reason being, Apache is just one of many web servers that are able to serve a TYPO3 site and we should not be auto-generating files that only work for one web server.

It may be more appropriate to include some sort of "should we fix this?" dialog if detecting that routing is broken and server is Apache, which turns into a link to documentation if the server is NOT an Apache server.

An alternative to creating such file would be to by default
generate links including the index.php like index.php/foo/bar/

And only skip the index.php file for url generation,
when an additional option (e.g. env var) is set.

That is the direction the Neos community went.

@Claus: of course we would not do that on non-apache web servers, that's what I meant with "capabilities". We are already delivering these files with the core and I'd argue that if you do not have a working config but a webserver capable of being auto configured it's nice if it works automatically if possible and informs you if not. As stated in the description for all other cases, I of course want some kind of hint.

BTW the introduction package already has this functionality since quite some time.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58451