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

2005-06-08 Thread Juliusz Chroboczek
Am I right when I say it's caching DNS server settings (from /etc/resolv.conf) or it's just caching the resolutions? It's caching both. How can I disable that? You cannot. You can invalidate cached DNS addresses by SIGUSR2-ing Polipo. You currently cannot invalidate the DNS server being

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

2005-03-25 Thread Tom Huckstep
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

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

2005-03-25 Thread 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

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

2005-03-24 Thread Radu Cristescu
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. /etc/polipo/config: proxyAddress = ::