[squid-users] TCP_CLIENT_REFRESH_MISS issue

hi,

i am using Squid Version 2.5.STABLE1 on linux-2.4.22/RedHat9 and i noticed
some weirdness, it could be a squid bug or it could be a mozilla bug or it
could be because i missed something obvious.

when using mozilla 1.5 (or 1.2) to download a file, mozilla seems to first
issue TCP_CLIENT_REFRESH_MISS on the HEAD. this happens when the save as
dialog box comes up and before the save button is pressed. when squid
receives this TCP_CLIENT_REFRESH_MISS on the HEAD it RELEASE the whole file
(not just the head) from the cache (the file was cached from a previous
download). when save is clicked mozilla sends a normal GET request and squid
says TCP_MISS (since it RELEASE the file already) and the file is fetched
from the origin server and stored in the cache once again.

it seems that squid RELEASE a cached file if it gets a
TCP_CLIENT_REFRESH_MISS on just the HEAD and not the actually GET, is this
correct behaviour ? my intuition tells me it is not as mozilla is probably
just trying to find out the file modification dates from the origin server
first before deciding on what to do next, either local cache or get from
network.

any comments would be appreciated :)

cheers,

alex

============================================
Alex Song
Software Engineer
Digital Stream USA, Inc.
44061 Nobel Drive
Fremont, CA 94538, USA
Work: (510) 770-5700 x266
Fax: (510) 770-5769
Email: asong@ds-usa.com
============================================
Received on Fri Nov 14 2003 - 16:29:26 MST