Issue Bug Closed

#63927Remove Last-Modified response header from cached output

Patrick Broens 12/16/14, 12:30 updated 10/02/18, 11:48

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

Reviews 2