wessels@nlanr.net said:
} I'd rather not introduce another option, but just make it the
} default behaviour to NOT cache responses with cookies.
Isn't there another problem here...
You start up on a service, it sends you a cookie to uniquely identify
you...
Subsequent requests to that service may result in pages which contain no
cookie, *but* vary according to the cookie which you are sending to the
service in your request headers.
This is a real swine since some people will use cookies to modify content
(which we therefore want to treat as private objects), and others will use
them to try and track what users are doing which I would prefer to defeat
by caching!!!
The easy solution is to not cache either pages with set-cookie headers and
pages resulting from requests with cookies embedded in the request header.
Unfortunately finding the percentage of pages in this latter catagory is
probably not possible without adding extra code into squid.
Nigel.
-- [ Nigel.Metheringham@theplanet.net - Unix Applications Engineer ] [ *Views expressed here are personal and not supported by PLAnet* ] [ PLAnet Online : The White House Tel : +44 113 251 6012 ] [ Melbourne Street, Leeds LS2 7PS UK. Fax : +44 113 2345656 ]Received on Mon Dec 16 1996 - 02:38:54 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:33:54 MST