In function httpParseHeaders()
...
if(!client &&
(name == atomSetCookie ||
name == atomCookie || name == atomCookie2))
cache_control.flags |= CACHE_COOKIE;
...
The cookie is ignored if it is a client request.
This makes the dontCacheCookies setting not apply to client request with
Cookie header
Many of the web server uses cookie to track session. The cookie directly
affect the content of the reply. The polipo cache only indexed by URL, it
lead to polipo serving pages to client on different sessions.
Should the "! client condition" removed from the above code? What would be
the implication if it is removed?
To me, if a request contains cookie, it should be handled by a privatized
object, unless there is ways to rule out possibility that the cookie has any
effect on the content of the reply.
Regards,
Ming
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Polipo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/polipo-users
