[TYPO3-ect] 4.1.0: Request parameters could not be validated
Elmar HInz
elmar.hinz at team.MINUS.red.DOT.net
Sun Mar 4 15:28:59 CET 2007
> Hi Elmar,
>
> this is a point i didn't understood at all.
> I fixed it in my installation by changing the default value in
> t3lib/config_default.php
> setting
> 'pageNotFoundOnCHashError' => 0,
>
> But i don't see the point what we can do to prevent this error.
>
> vg Steffen
Hi Steffen,
http://typo3.org/extensions/repository/view/lib/0.0.20/info/class.tx_lib_controller.php/
// Initialize the cHash system if there are parameters available
if ($GLOBALS['TSFE'] && $parameters->count()) {
$GLOBALS['TSFE']->reqCHash();
}
Currently we do the cHash test by default independently if it is a USER
or a USER_INT. But maybe that is our fault:
USER + cHash + reqCHash: Fine the page is cached.
USER_INT + no cHash + reqCHash: Also works.
But: The page should be cached with a marker for USER_INT. Is it?
Or is it completely rerendered each time because of reqCHash? I am not
sure in the moment. I fear I need to dig into that stuff again. So
complicated. So quickly forgotten.
Now the question of a solution:
I fear with this we have to set reqCHash only if it is a USER object and
unset if for USER_INT. For that the controller needs to find out itself if
it is a USER or USER_INT. But how? Manual setting would be a simple but
ugly solution. Then we would end up with the same confusing settings
like tslib_pibase.
Regards
Elmar
More information about the TYPO3-team-extension-coordination
mailing list