Bug#301228: polipo: source file out of date but popilpo reports 304 Not modified
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 used other than by restarting Polipo. A workaround is to use a local caching-only DNS server. I use pdnsd on all of my machines. Tom, could you please downgrade this bug to wishlist status? Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301228: polipo: source file out of date but popilpo reports 304 Not modified
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]
Bug#301228: polipo: source file out of date but popilpo reports 304 Not modified
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]
Bug#301228: polipo: source file out of date but popilpo reports 304 Not modified
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 = :: proxyPort = 8123 allowedClients = 0.0.0.0/0 logFile = /var/log/polipo.log Client request: | GET http://deb.plutohome.com/debian/dists/20dev/main/binary-i386/Packages.gz HTTP/1.1 | Host: deb.plutohome.com | Cache-Control: max-age=0 | If-Modified-Since: Fri, 18 Mar 2005 18:42:39 GMT | User-Agent: Debian APT-HTTP/1.3 | Connection: close Server answer header: | HTTP/1.1 200 OK | Date: Thu, 24 Mar 2005 14:07:15 GMT | Server: Apache/2.0.52 (Debian GNU/Linux) DAV/2 SVN/1.1.3 PHP/4.3.10-2 | Last-Modified: Wed, 23 Mar 2005 20:46:58 GMT | ETag: 988005-1b61-fef7480 | Accept-Ranges: bytes | Content-Length: 7009 | Connection: close | Content-Type: text/plain | Content-Encoding: x-gzip But polipo says this: | HTTP/1.1 304 Not modified | Connection: close | Date: Thu, 24 Mar 2005 14:05:38 GMT | ETag: 2db6a6-1b3c-be2345c0 I added relaxTransparency = maybe to the config file, restarted polipo, and then it revalidated the file when requested. This could be conjunctural though. PS. That allowedClients is shielded by a firewall, so it's not really an open proxy. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages polipo depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
