TYPO3 Core

I can reconstruct this issue.
It disappears, when clearing the frontend cache, then the redirects work as expected.

But as soon as I call the front page (the first page in rootLine, which contains the TypoScript setup) and this page gets cached, the redirect break, with the exception from above.

I tried several TYPO3 versions. This issue seems to occure since 12.4.2. In 12.4.1 I am not able to reconstruct the issue, by calling the first page in rootLine (the front page). There, the redirections always work.

A quick fix is, to disable caching on the first page in rootLine, with e.g.

# Quick fix for https://forge.typo3.org/issues/102892
[traverse(page, "uid") == 1]
config.no_cache = 1
[end]

I also found the commit, which causes the issue:
https://git.typo3.org/typo3/typo3/-/commit/bd4980f237bf844939b959d0a83909aa7a44b0e0

The issue only occures when the feature toggle "Security: frontend enforce content security policy" [security.frontend.enforceContentSecurityPolicy] is disabled.

I don't think this is related to CSP, but more related to cached TypoScript (I might look into this during the next few days/weeks):
https://github.com/TYPO3/typo3/blob/a085e88596eacb3f2e12bdd49d2f3e7a47faed2c/typo3/sysext/core/Classes/TypoScript/FrontendTypoScript.php#L132-L138

Some more notes:

This is related to a fully cached page not having TypoScript anymore, see another issue / bugfix which happened in adminpanel on a fully cached page:

https://review.typo3.org/c/Packages/TYPO3.CMS/+/82396

@Oliver Hader So, when CSP is on the page cache does not work anymore? Sounds a little bit like that.

@Benni Mack Caching and providing the rendered Typoscript configuration, could solve this, maybe?

Or the redirect Middleware must get enabled to parse the Typoscript, when being triggered and when the target starts with "t3:".

But maybe there are other edge cases, like redirects, which require the parsed Typoscript config.