>>> < Expires: never
> <<Expires: never>> as in "this page shall never expire!".
Em, no. "Expires: never" is treated by Polipo as "Expires: 0", meaning
that the page is not cached. This behaviour is actually mandated by
RFC 2616 14.21:
HTTP/1.1 clients and caches MUST treat other invalid date formats,
especially including the value "0", as in the past (i.e., "already
expired").
So the headers sent by the server are correct, if somewhat confusing.
Ideally, the server should do the following:
To mark a response as "already expired," an origin server sends an
Expires date that is equal to the Date header value.
The issue is with something else, and it would be good to work it out.
For what it's worth, I cannot reproduce it on my side.
Juliusz
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
