We have set up squid to pass authetication requests to the origin server
(squid authentication
is not activated )  and for the first request, everything works as
expected - 
-- squid sends the authentication  request to the origin server 
-- after successful authentication, squid  retrieves the object in the
request. 
-- Subsequent requests to squid for the same object are returned by
squid (from its cache) without going to the origin server.
 
When we request the same object from a different browser session or from
a different user, this is what happens:
-- squid sends teh request to the origin server for authentication 
-- after  successful authentication, squid retrieves the same object
from the origin server

 
Here's what I see in the access log
------------------------------------------------------------------------
-------------
Here's the access log from the origin server
 
135.16.148.59 - - [02/Feb/2007:16:18:28 -0500] "GET /pat/ HTTP/1.1" 401
401
135.16.148.59 - pat [02/Feb/2007:16:18:36 -0500] "GET /pat/ HTTP/1.1"
200 366
135.16.148.59 - pat [02/Feb/2007:16:21:07 -0500] "GET /pat/overview.pdf
HTTP/1.1" 304 
........
I requested the same object multiple times and nothing was logged here [
origin server log ] which is good
 
Now I opened a new browser and did the same request - and you can see
that the same object was
re-requested by Squid [ and not served from its cache]

135.16.148.59 - - [02/Feb/2007:16:21:29 -0500] "GET /pat/ HTTP/1.1" 401
401
135.16.148.59 - pat [02/Feb/2007:16:21:39 -0500] "GET /pat/ HTTP/1.1"
200 366
135.16.148.59 - pat [02/Feb/2007:16:21:45 -0500] "GET /pat/overview.pdf
HTTP/1.1" 304
------------------------------------------------------------------------
-------------
 
Thanks for your help.
 
[EMAIL PROTECTED]

Reply via email to