[TYPO3-dev] Core Behaviour: Using Cache-Control Headers to prevent _Clients_ from Caching

Martin Kutschker Martin.Kutschker at n0spam-blackbox.net
Tue Nov 21 16:12:23 CET 2006


Ekkehard Gümbel schrieb:
> Martin Kutschker schrieb:
> 
>> So I don't see what's wrong with my config proposal. If the page is 
>> not cachable TYPO3 shall send no-cache in any case, but if it's 
>> cachable apply logic as requested by sendCacheHeaders.
> 
> Is guess that is the point: What I am trying to discuss is the behaviour 
> of the "page is not cachable" case!
> 
>  > If the page is not cachable TYPO3 shall send no-cache in any case
> Is that so? Then no need to talk further, let's just change the 
> behaviour without any configurables.

You mean use "no-cache" instead of "private"?

> My point was that some (like Ole) MAY want to allow private caching but 
> not proxy caching, though.

Something I don't understand in the current code. Private caching makes 
only sense if I set a max age otherwise it's odd that TYPO3 explicitely 
allows client side caching of non-cachable data.

Masi




More information about the TYPO3-dev mailing list