> # cat *
> HTTP/1.1 404 Not Found
> Content-Length: 5043
> Date: Mon, 19 Oct 2009 16:42:26 GMT
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Cache-Control: private
> Content-Type: text/html; charset=ISO-8859-1
> Server: gws
> X-XSS-Protection: 0
> X-Polipo-Location: http://www.google.com/12345
> X-Polipo-Access: Mon, 19 Oct 2009 16:42:26 GMT
> X-Polipo-Body-Offset: 768
That's the expected behaviour.
``Uncachable'' in Polipo means that it will be revalidated on the next
access. An uncachable object is still stored on disk, but Polipo will
contact the origin server before serving it to a client.
Please let me know if you actually see stale data from Polipo; just
having Polipo optimise things by storing a local copy of uncachable data
is certainly not a bug.
Juliusz
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
