Bug#301228: polipo: source file out of date but popilpo reports "304 Not modified"

[Uplink]

Looks like what happened wasn't from the content validation part of 
polipo. It's that polipo seems to cache the DNS settings and I was 
changed them on the fly, which caused me to report this. In fact, polipo 
was only interrogating the old DNS it knew and ignored me completely. 
Changing the settings required a restart and that's why it worked after 
that.

Am I right when I say it's caching DNS server settings (from 
/etc/resolv.conf) or it's just caching the resolutions? How can I 
disable that?

Then I should close this bug, since it's mostly a false alarm.
Tom Huckstep wrote:
On Thu, Mar 24, 2005 at 04:38:07PM +0200, Radu Cristescu wrote:
 

Package: polipo
Version: 0.9.6-1
Severity: important
Server reports a Last-Modified date newer than the one of the cache
file, but polipo reports that it was not modified and serves the out of
date file even if a If-Modified-Since header is supplied.
   

Can you replicate this with the latest version, 0.9.8-1?
Tom
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]