Re: Polipo - disabling the cache

> Hmm. Ok, alternatively, how to completely flush and mark void
> the cache? But it is not optimum, see below.

kill -USR2 $(cat /var/run/polipo.pid); rm -rf /var/cache/polipo/*; kill -USR2 $(cat /var/run/polipo.pid)


If you're running with no on-disk cache, just the kill.

> I ran into a situation with web requests from around the globe. Since polipo
> cached the page, but the page depends on where it is fetched from,
> polipo doesn't know that and I get the cached version.

Then the server should mark the page as ``Cache-Control: private'', and
Polipo will revalidate it on every access (assuming cacheIsShared is set
to false, as it is by default).

If it is not, you can force Polipo to revalidate it by putting the right
regexp into /etc/polipo/uncachable.  Of course, if the server is buggy,
it may spuriourly reply true to revalidation (e.g. because it implements
ETags incorrectly), in which case you're still SOL.

-- Juliusz

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct