On Tue, 8 Mar 2005, razidan wrote:
> I used 'tail -f -n 100 access.log' to check the access log and i still see the
> following lines:
>
> 1110244681.832 � �719 192.168.0.14 TCP_MISS/200 3365 GET
> http://www.hp.com/country/us/en/img/n4_welcome/hho/b1_hho_text.gif -
> DIRECT/161.114.22.111 image/gif
[...]
All of these were cache misses. None were cached, or at least none were
served from the cache (access.log does not tell what was cached, only how
the specific request was resolved).
> I think if the lines are visible in access.log for 192.168.0.14, then its
> being cached, correct me if i'm wrong pls.
This just says the requests was proxied by Squid and that all the requests
were cache misses.
If you do not want Squid to at all proxy the requests but instead have the
browser talk directly to the origin server then you must not send the
requests to Squid in the first place.
Regards
Herik
Received on Mon Mar 07 2005 - 19:46:38 MST
This archive was generated by hypermail pre-2.1.9 : Fri Apr 01 2005 - 12:00:02 MST