default_ttl applied even when Expires exist

2008-04-20 Thread Ricardo Newbery
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

varnish and logging

2008-04-20 Thread Timothy Ball
I have a pretty basic setup w/ varnish load balancing infront of apache. The problem I am experiencing is that the apache logs themselves seem *really* off (hit rates are nearly one order of magnitude low). So I examined the varnishlog(1) man pages... Does anyone have a script that takes

Re: default_ttl applied even when Expires exist

2008-04-20 Thread Ricardo Newbery
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

Re: default_ttl applied even when Expires exist

2008-04-20 Thread Ricardo Newbery
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