Bug #63927

Story #63815: Reduce communication between server and client

Remove Last-Modified response header from cached output

Added by Patrick Broens about 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Must have
Category:
-
Target version:
-
Start date:
2014-12-16
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The current state of last-modified is broken by design.

Furthermore it is the question if we should support this properly at all in the future, since well, the whole page has to be rendered anyway to find out if it 'was-modified-since' so there is no benefit on server side (and not on client side either). Supporting that would also mean that we need to track/hash basically everything, so it would be a really evil cross-cutting-concern that affects extensions, content, files, everything.

A document is added to this issue explaining the whole situation


Files

Browser caching.pdf (71.5 KB) Browser caching.pdf Patrick Broens, 2014-12-16 12:30

Also available in: Atom PDF