TYPO3 Core

You should read the article named "Misteries of cHash". Google for it. In your case cHash is required if you want to see proper records. No other way.

Thank you for replying to this. I think right now we are in a very bad situation (at least in our agency we have lots of trouble because of this). I did not mention about the connection to realUrl yet because I think the problem is clearly on TYPO3-core-side right now. But it has to do with the current realUrl-version, especially when an editor previews his own new news-article and is logged into the backend the same time. We cannot prevent them from being logged in and so we run into the problems because TYPO3 caches the page then.
Also we need to clear the urlcache sometimes especially after subtree-movements so we cannot rely on the urlcache to have the cHash stored and I think a "cache" is not the place for persistent data. So I think this is a core-bug that there is not at least an option to prevent a page from being cached when there are any GET-params (except of those in [FE][cHashExcludedParameters]) and NO cHash.

• I need to maintain a list of get-parameters of all my plugins and still think of this when I install another extension one day
• incorrect cHashes also dont trigger an 404-error anymore

If only I could put "*" into [FE][cHashRequiredParameters] I would be (half) happy already.

Any other solution is welcome how to get around this problem.

This is NOT a bug of the core but of your implementation :) You are REQUIRED to generate links with cHash if your plugins use parameters and they are cached. It is fully your responsibility. TYPO3 may not guess what you want to do in your plugin or your TypoScript. It just does what you asked it to do. If you forgot a useCacheHash for typolink, you will get the behavior you describe. In such case the behavior is as expected!

You should check your code and your TypoScript and find what makes links without cHash.

As to realurl, switch to 2.1.4. This should solve at least half of cases with missing cHash.

This is NOT a bug of the core but of your implementation :) You are REQUIRED to generate links with cHash if your plugins use parameters and they are cached. It is fully your responsibility. TYPO3 may not guess what you want to do in your plugin or your TypoScript. It just does what you asked it to do. If you forgot a useCacheHash for typolink, you will get the behavior you describe. In such case the behavior is as expected!

I know how to create the links with the chash-parameter, that is not the problem here. The problem is the behaviour when the cHash is missing. Just caching the page and deliver it from cache on the next is just not right.

You should check your code and your TypoScript and find what makes links without cHash.

Everybody can strip that parameter off from the url, so I dont have control about that. I like my system to react properly in those cases. But that is hard to do if there is no option and TYPO3 just caches.

As to realurl, switch to 2.1.4. This should solve at least half of cases with missing cHash.

Thanks for that, this is a good information. Will have read the code in the commits or is there somewhere a changelog?