Bug #102445
closedTYPO3 does not restrict content with non-cacheable content to be stored in a client or proxy
100%
Description
By default, TYPO3 does not send the HTTP Header "Cache-Control: private, no-store" when a USER_INT plugin
is sent. This can lead to very annoying issues when using proxies. The headers are only sent when config.sendCacheHeaders = 1
is set.
The option is now reduced to only affect pages which are explicitly possible to be cached on a client
to send custom and additional cache headers.
Updated by Gerrit Code Review 9 months ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/81840
Updated by Gerrit Code Review 9 months ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/81840
Updated by Gerrit Code Review 9 months ago
Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/81840
Updated by Gerrit Code Review 9 months ago
Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/81840
Updated by Gerrit Code Review 9 months ago
Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82016
Updated by Benni Mack 9 months ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 594c1cd43afe2f052faa4ec092e04b94658ee889.