RE: TCP_MISS/200 and TCP_MISS/304

C.W.,

the .pl script isn't cacheable, and shouldn't be. That, however, leaves the
images. The TCP_MISS/200's are MISSs as you'd think; they aren't in the
cache, and the proxy sends the complete response that it gets from the
server.

However, TCP_MISS/304 is a bit different; what this means is that it isn't
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.

Does this help?

> -----Original Message-----
> From: C. W. Wright [mailto:wright@betaweb.com]
> Sent: Wednesday, April 28, 1999 11:51 AM
> To: squid-users@ircache.net
> Subject: TCP_MISS/200 and TCP_MISS/304
>
>
>
> Greetings!
>
> I've had squid 2.2 installed for a week or so now on my home
> network which
> consists of one linux system (200mhz pentium 64mb 8gb disk),
> three windoze
> machines, and a an old sun which is used as an X-terminal. I
> have squid
> setup to use 800mb or disk for the queue.
>
> It appears things are not being cached as expected. For example, I
> frequently use: http://weather.noaa.gov/cgi-bin/mgettaf.pl which
> references several gif images which certainly should be cached by now
> since I use this URL daily. Here's what the access log shows:
>
>
> 925262497.612 9257 127.0.0.1 TCP_MISS/200 4444 POST
> http://weather.noaa.gov/cgi-bin/mgettaf.pl - DIRECT/weather.noaa.gov
> text/html
> 925262502.332 4708 127.0.0.1 TCP_MISS/200 1611 GET
> http://weather.noaa.gov/graphics/faq.gif - DIRECT/weather.noaa.gov
> image/gif
> 925262503.162 5546 127.0.0.1 TCP_MISS/200 1687 GET
> http://weather.noaa.gov/graphics/search.gif - DIRECT/weather.noaa.gov
> image/gif
> 925262504.372 7489 127.0.0.1 TCP_MISS/200 1801 GET
> http://weather.noaa.gov/graphics/nwslink.gif - DIRECT/weather.noaa.gov
> image/gif
> 925262504.732 2398 127.0.0.1 TCP_MISS/200 1612 GET
> http://weather.noaa.gov/graphics/feedback.gif -
> DIRECT/weather.noaa.gov
> image/gif
> 925262510.322 16005 127.0.0.1 TCP_MISS/200 21169 GET
> http://weather.noaa.gov/graphics/ban12t.gif - DIRECT/weather.noaa.gov
> image/gif
> 925262806.622 3044 127.0.0.1 TCP_MISS/200 6059 POST
> http://weather.noaa.gov/cgi-bin/mgetmetar.pl - DIRECT/weather.noaa.gov
> text/html
> 925262807.014 682 127.0.0.1 TCP_MISS/304 267 GET
> http://weather.noaa.gov/graphics/reverse.gif - DIRECT/weather.noaa.gov
> image/gif
> 925263382.402 2865 127.0.0.1 TCP_MISS/200 6059 POST
> http://weather.noaa.gov/cgi-bin/mgetmetar.pl - DIRECT/weather.noaa.gov
> text/html
>
>
> The above entry is the last entry after using the link (from netscape)
> several times today. There are TCP_MEM_HIT/200 and
> TCP_REFRESH_MISS/200
> in the logs, but the TCP_MISS/200 seems to rule, even on
> links that are
> very static such as gif images. Anyone have any ideas???
>
>
> Regards,
> C. W. Wright
>
>
Received on Wed Apr 28 1999 - 00:25:38 MDT