TYPO3 Core

I just noticed that ProductionExceptionHandler tries to handle ImmediateResponseException by rendering an "Oops, an error occurred" string. From what I understand this is not correct, the handler should at least relay the exception so that it can be handled accordingly.

Doc comment says:

/**
 * Exception that has to be handled immediately in order to have
 * stop current execution and provide the current response. This
 * exception is used as alternative to previous die() or exit().
 *
 * @internal
 */

An ImmediateResponseException is for example thrown on cHash validation errors when pageNotFoundOnCHashError is set to "true" which then leads to Oops messages being cached when a user serves to an uncached page with an unknown GET param...

This only happens when TYPO3 is running in Production mode or the ProductionExceptionHandler is used in Dev / Staging context.