On Apr 20, 2008, at 10:33 PM, Poul-Henning Kamp wrote:
In message 8240BA9F-
[EMAIL PROTECTED], Ricardo N
ewbery writes:
I see in rfc2616.c that this behavior is intentional. Varnish
apparently assumes a clockless origin server if the Expires date
is not in the future and then applies
Noticed some odd behavior.
On page with an already-expired Expires header (Expires: Sat, 1 Jan
2000 00:00:00 GMT) and no other cache control headers, a stock install
of Varnish 1.1.2 appears to be applying the built-in default_ttl of
120 seconds when instead it should just immediately
On Apr 20, 2008, at 2:44 AM, Ricardo Newbery wrote:
Noticed some odd behavior.
On page with an already-expired Expires header (Expires: Sat, 1 Jan
2000 00:00:00 GMT) and no other cache control headers, a stock install
of Varnish 1.1.2 appears to be applying the built-in default_ttl of
120
On Apr 20, 2008, at 12:28 PM, Ricardo Newbery wrote:
On Apr 20, 2008, at 2:44 AM, Ricardo Newbery wrote:
Noticed some odd behavior.
On page with an already-expired Expires header (Expires: Sat, 1 Jan
2000 00:00:00 GMT) and no other cache control headers, a stock
install
of Varnish
