Project

General

Profile

Actions
Copy link

Bug #90973

open
« Previous | 1 of 8 | Next »

cHash is generated with useCacheHash = 0

Added by Franz Holzinger about 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2020-04-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.

Files

patch-90973.diff (3.24 KB) patch-90973.diff Franz Holzinger, 2020-04-07 16:16
Actions
Copy link
 #1

Updated by Franz Holzinger about 4 years ago

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.

Actions
Copy link
 #2

Updated by Benjamin Robinson about 4 years ago

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?

Actions
Copy link
 #3

Updated by Franz Holzinger over 3 years ago

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.

Actions
Copy link

Also available in: Atom PDF