PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » HTTP » HTTP_Header » Bug #6616

Wrong implementation of expiration model of HTTP-Cache

Details

Submitted2006-01-29 09:40 UTC
Fromgugglegum at gmail dot com
StatusBogus
PackageHTTP_Header
PHP VersionIrrelevant
OSIrrelevant
Roadmaps(Not assigned)

Comments

[2006-01-29 09:40 UTC] gugglegum at gmail dot com

Description:
------------
HTTP_Header_Cache redefines Cache-Control header to 'private, must-revalidate, max-age=0'.

First of all, "private" - indicates that the response must not be cached in shared cache. This is case-specific, anonymously-accessed pages should have "public" directive.

In second, directives "must-revalidate" and "max-age=0" requires revalidation of cache entry every time. So "expiration time" actually ignored by cache and expiration model of HTTP cache (in RFC-2616) does not work properly.