Issue Bug Closed

#78068Page get cached when called without cHash-param

Peter Rauber 09/26/16, 15:31 updated 01/13/20, 13:32

Description

Steps to reproduce:
  • install an extensions (like news)
  • create 2 news entries
  • place the news-plugin (and set the storage of the news-entries)
  • call the page of a news-entry (without cHash-param) i.e. index.php?id=1&tx_news_pi1%5Bnews%5D=1&tx_news_pi1%5Bcontroller%5D=News&tx_news_pi1%5Baction%5D=detail
  • call the page again without cHash, but for another news-id: index.php?id=1&tx_news_pi1%5Bnews%5D=2&tx_news_pi1%5Bcontroller%5D=News&tx_news_pi1%5Baction%5D=detail

Expected Result:
On the 1st call, you see the 1st news-entry, on the second call, you see the 2nd news-entry

Actual Result:
You see on both calls the 1st news-entry (because it gets cached in the 1st call)

So: Why does TYPO3 cache the page when there are different get-parameters sent? I understand the cHash-system, but there are situations when the cHash is NOT present and I want my system to render a proper page even in those cases.

Reviews 0

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