TYPO3 Core

Here is my current setup:

Extbase-routeEnhancer (default news detail):

  Blogposts:
    type: Extbase
    limitToPages: [292]
    extension: News
    plugin: Pi1
    routes:
      - { routePath: '/{news_title}', _controller: 'News::detail', _arguments: {'news_title': 'news'} }
    aspects:
      news_title:
        type: PersistedAliasMapper
        tableName: 'tx_news_domain_model_news'
        routeFieldName: 'path_segment'

1) clear cache
2) /base/someArticle?lala=1 -> cHash validation failed (as expected)
3) /base/someArticle -> cHash validation failed

4) clear cache
5) /base/someArticle -> OK (as expected)
6) /base/someArticle?lala=1 -> OK (should throw cHash error)

So basically the first call of the plugin gets cached. Any subsequent call will reproduce the same result (which is ok for most parameters, but not for the cHash validation itself!)

This affects 9.5 and master.

It is not reproducible for plain (non-enhancer) plugin URLs.

I discovered it when reviewing this bug some weeks ago:

https://review.typo3.org/c/Packages/TYPO3.CMS/+/60296 (cHash calculation respects excludedParameters for enhancers)

But it was out of scope there and I forgot to submit a bug report. Now I experienced it on a live v9 site.