Project

General

Profile

Actions
Copy link

Bug #102445

closed

TYPO3 does not restrict content with non-cacheable content to be stored in a client or proxy

Added by Benni Mack 8 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Should have
Assignee:
Benni Mack
Category:
Frontend
Target version:
13.0
Start date:
2023-11-22
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.

Actions
Copy link

Also available in: Atom PDF