Issue Bug Closed

#88070URL with extbase action and additional query string throws error using route enhancer

Chris Müller 04/04/19, 10:05 updated 08/29/19, 14:54

Description

I have a page that shows a single record of an extbase action, e.g. the URL is /job/developer/. job is the slug of the page with the plugin and developer is the path segment for the route enhancer aspect.

When I call this URL the content is shown correctly. Now I add a query string like ?utm_campaign=google_jobs_apply and get a cHash validation error (results in a 404 page, $GLOBALS['TYPO3_CONF_VARS']['FE']['pageNotFoundOnCHashError'] is set to true). utm_campaign is whitelisted in $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['excludedParameters'].

I tracked it down to TypoScriptFrontendController->reqCHash(). In the first case $this->pageArguments->getDynamicArguments() is empty, so the further processing of the method is skipped. In the second case with the query string the dynamic arguments are not empty (filled with utm_campaign) which results in the further processing of the method and throws an exception.

When I disable the route enhancer the extbase query strings with chash are working correctly with additional utm parameters.

Reviews 0

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