Issue Bug Closed

#90973cHash is generated with useCacheHash = 0

Franz Holzinger 04/07/20, 15:55 updated 05/27/24, 19:39

Description

The page router does not check if the configuration of useCacheHash = 0. Always a cHash is generated and added to the url. This causes a problem with an Ajax call, because it causes an error with the cHash resolution:

*Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1518472189: Request parameters could not be validated (&cHash comparison failed) *

Therefore I always turn the cHash configuration off for a Ajax url with eID parameter set, and as well no_cache=1.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 4

  1. Franz Holzinger commented and changed attached patch-90973.diff 04/07/20, 16:18

    This patch does not add the cHash parameter by default. Only when useCacheHash has been set to 1 in the typolink call, the cHash paramter is generated. This has been the behaviour from all former versions of TYPO3.

  2. Benjamin Robinson commented 04/17/20, 09:39

    I just failed to rewrite a TypoScript generated GET parameter with a routEnhancer without appending a cHash ( Code-Example at Stack Overflow ). Could this be related to this bug?

  3. Franz Holzinger commented 10/10/20, 11:17

    Ben Robinson, yes, I assume that every link which is wrongly generated without the cHash parameter in TYPO3 9.5 has to do with this issue. After all this could be the reason for this misbehaviour.

  4. Georg Ringer commented and changed status New Closed 05/27/24, 19:39

    see #91473 which dropped useCacheHash in v11. therefore closing the issue