=20
>=20
> here is some debug from my access.log:
> -------------
> 1081924400.238 778 192.168.2.252 TCP_MISS/304 180 GET=20
> http://www.samba.org/samba/samba.html -=20
> DEFAULT_PARENT/proxy.kennisnet.nl -
> 1082102628.436 695 192.168.2.252 TCP_MISS/304 122 GET=20
> http://www.samba.org/samba/samba.html -=20
> DEFAULT_PARENT/proxy.kennisnet.nl -
> 1082102632.069 217 192.168.2.252 TCP_MISS/304 122 GET=20
> http://www.samba.org/samba/samba.html -=20
> DEFAULT_PARENT/proxy.kennisnet.nl -
> -------------
> all of the lines in the logfile has the TCP_MISS and DEFAULT_PARENT
> thing.. (i tested www.samba.org to see if the site is cacheable, and
> it is!!)
>...
>...

=20
TCP_MISS/304 means that the object=20
in the Squid cache, but it is in your browser's cache. Your browser will
submit a If-Modified-Since request to Squid, which will forward it on to =
the
origin server. If the object hasn't been modified, it'll get a 304, =
which
Squid will pass on to your browser. However, Squid doesn't have a copy
itself, therefore TCP_MISS.

You need to make a test setup with 2 >different< browsers subsequently=20
'entering' that site and this from 2 >different< sources (IP's)=20
; in my case this results in :


First access
----------------

1082104494.511 450 xxxxxxxxxxxxxx TCP_MISS/200 5301 GET =
http://www.samba.org/ - DIRECT/www.samba.org text/html
=20
Subsequent access from another squid client
---------------------------------------------

1082104561.300 4 xxxxxxxxxxxxxxxx TCP_MEM_HIT/200 5309 GET =
http://www.samba.org/ - NONE/- text/html


M.