Squid cannot cache content requiring authentication. This is a very
strict requirement in the HTTP specification to avoid private content to
be inadvertly caches and accessed by unauthorized users.
How I can tell that the request requires authentication: There is two
requests where the first is a 401 reply, clearly indicating that the
server requires the user to authenticate before being given access to
the requested resource.
If you enable "log_mime_hdrs" then you should also notice a
"Authorization" header in the second request. (note: Never post such
headers in public forums as they contain the users login and password in
slightly but easily decoded obfuscated plain text)
Regards
Henrik Nordström
Squid Developer
"SRILAKSHMANAN,LAKSHMAN (HP-Australia,ex3)" wrote:
>
> Hi all,
>
> Why is squid not caching http request? I always get TCP_MISS..!!!
>
> 1015286365.529 1 15.73.168.201 TCP_MISS/401 743 GET
> http://panther.aus.hp.com/soar.tar - DIRECT/panther.aus.hp.com text/html
> 1015286377.137 5672 15.73.168.201 TCP_MISS/200 2171213 GET
> http://panther.aus.hp.com/soar.tar - DIRECT/panther.aus.hp.com
> application/x-tar
>
Received on Mon Mar 25 2002 - 20:20:50 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:07:05 MST