Re: Squid vs Browser cache

On Sat, Feb 19, 2000 at 09:07:56AM -0500, Subba Rao wrote:
>
> Please look at the following messages to the same site from 2
> different machines.
>
> >From Linux:
>
> 950968381.349 1293 127.0.0.1 TCP_MISS/200 4390 GET http://www.squid-cache.org/ root
> +DIRECT/www.squid-cache.org text/html
> 950968383.566 1939 127.0.0.1 TCP_MISS/200 2125 GET http://www.squid-cache.org/Icons/squidnow.gif
> +root DIRECT/www.squid-cache.org image/gif
> 950968383.706 2036 127.0.0.1 TCP_MISS/200 856 GET http://www.squid-cache.org/Icons/cache_now.gif
> +root DIRECT/www.squid-cache.org image/gif
> 950968384.345 2842 127.0.0.1 TCP_MISS/200 10902 GET http://www.squid-cache.org/Squidlogo2.gif root
> +DIRECT/www.squid-cache.org image/gif
>
>
> >From NT:
>
> 950968451.495 2 127.0.0.1 TCP_MEM_HIT/200 4398 GET http://www.squid-cache.org/ root NONE/-
> +text/html
>
>
> What the TCP_MISS and TCP_MEM_HIT flags? For the NT machine, the page
> is instantly delivered, but for Linux Squid fetches the page. Both
> the machines are pointing to the same port on the Linux box.

Running Netscape, right?

It's an FAQ - there is a bug/misdesign in the Linux version Netscape
such that when you select a bookmark it forces end-to-end reload of the
target. Not much that can be done about it, unfortunately.

  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  cliftonr@lava.net
      The named which can be named is not the Eternal named.