#17115Wrong &chash values should trigger an error
Description
TYPO3 uses a parameter “&cHash” to cache different views of the same page (e.g. a plugin containing a record browser).
If the &cHash parameter is wrong, someone has most likely modified a link generated by TYPO3 manually.
The behaviour for such a case can be changed through $TYPO3_CONF_VARS[‘FE’][‘pageNotFoundOnCHashError’]. Up to TYPO3 4.1, this is set to false which means that no error is triggered, but caching will be disabled for that page.
This is a new attempt for fixing a known problem. The fix was in TYPO3 between 4.1beta2 and 4.1RC2, but was reverted recently before 4.1 final.
The reason for reverting it was that many buggy extensions have always worked fine even though the chash value was wrong. They just had no_cache enabled, so most likeley nobody noticed.
By reintroducing the patch for TYPO3 4.2 I want to give extension authors several months time to fix their eventually broken extensions.
(issue imported from #M5209)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.