[TYPO3-core] RFC: #16737: sendCacheHeaders: Wrong usage of Pragma: public and no-cache

Bjoern Pedersen bjoern.pedersen at frm2.tum.de
Tue Dec 14 14:30:52 CET 2010


Am 14.12.2010 14:06, schrieb Jigal van Hemert:
> Hi,
> 
> On 14-12-2010 13:48, Martin Kutschker wrote:
>> Am 14.12.2010 13:30, schrieb Georg Kuehnberger:
>>> Accoring to my understanding "Pragma: public" is wrong accoring to
>>> the RFC, and pretty much useless,
>>> as it should not be interpreted by any client or intermediary cache.
>>> (wrong+useless = bug, to me).
> (...)
>> Redbot errs in its report. The relevant part of the RFC allows any
>> token (as extension pragma).
> 
> I agree with Masi here. The fact that the RFC hasn't defined 'public' as
> a possible value does not mean that no machines in the request-result
> chain will use it.
> 
> So it is not "wrong" and I can't say for certain that it is "useless"
> either. Unless there is evidence of a problem or error somewhere (a
> certain proxy acts incorrect, etc.) I would not remove any directive.
> 
> "If it ain't broken don't fix it."
> 
> So, for now -1 .
> 
Looking at
http://php.net/manual/de/function.header.php and
http://joseph.randomnetworks.com/2004/10/01/making-ie-accept-file-downloads/

it seems that IE needs this Pragma: Public for caching on
https-connections, as IE by default does not cache (or in any other way
save to disk) any encrypted content.

So it should stay there unless a real problem gets reported.

-1 from me.

Björn


More information about the TYPO3-team-core mailing list