hi henrik,
here are the outputs, i censored the url cuz i am paranoid.
1068854016.259 620 192.168.46.222 TCP_CLIENT_REFRESH_MISS/200 305 HEAD
http://xxxxxx - DIRECT/130.94.72.145 video/xvd [Host:
www.ds-usa.com\r\nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0;
en-US; rv:1.5) Gecko/20031007\r\nAccept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=
0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1\r\nAccept-Language:
en-us,en;q=0.5\r\nAccept-Encoding: gzip,deflate\r\nAccept-Charset:
ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nKeep-Alive: 300\r\nProxy-Connection:
keep-alive\r\nPragma: no-cache\r\nCache-Control: no-cache\r\n] [HTTP/1.1 200
OK\r\nDate: Fri, 14 Nov 2003 23:58:23 GMT\r\nServer: Apache/1.3.24
(Unix)\r\nLast-Modified: Thu, 10 Apr 2003 19:09:35 GMT\r\nETag:
"20708e-a852a3-3e95c16f"\r\nAccept-Ranges: bytes\r\nContent-Length:
11031203\r\nKeep-Alive: timeout=15, max=200\r\nConnection:
Keep-Alive\r\nContent-Type: video/xvd\r\n\r]
1068854094.331 66041 192.168.46.222 TCP_MISS/200 11031508 GET http://xxxxxx
- DIRECT/130.94.72.145 video/xvd [Host: www.ds-usa.com\r\nUser-Agent:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
Gecko/20031007\r\nAccept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=
0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1\r\nAccept-Language:
en-us,en;q=0.5\r\nAccept-Encoding: gzip,deflate\r\nAccept-Charset:
ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nKeep-Alive: 300\r\nProxy-Connection:
keep-alive\r\nPragma: no-cache\r\nCache-Control: no-cache\r\n] [HTTP/1.1 200
OK\r\nDate: Fri, 14 Nov 2003 23:58:35 GMT\r\nServer: Apache/1.3.24
(Unix)\r\nLast-Modified: Thu, 10 Apr 2003 19:09:35 GMT\r\nETag:
"20708e-a852a3-3e95c16f"\r\nAccept-Ranges: bytes\r\nContent-Length:
11031203\r\nKeep-Alive: timeout=15, max=199\r\nConnection:
Keep-Alive\r\nContent-Type: video/xvd\r\n\r]
there seems to be no-cache directives in both of them. if so shouldn't
TCP_MISS be TCP_CLIENT_REFRESH_MISS instead ? or is that because the file is
already released from the cache ? this is not that important.
but the file still gets released after the TCP_CLIENT_REFRESH_MISS on the
HEAD, i still feel that this is not 100% good. what do you think ?
thanks,
alex
> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Sent: Friday, November 14, 2003 3:47 PM
> To: Alex Song
> Cc: 'squid-users@squid-cache.org'
> Subject: Re: [squid-users] TCP_CLIENT_REFRESH_MISS issue
>
>
> On Fri, 14 Nov 2003, Alex Song wrote:
>
> > 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.
>
> If you enable log_mime_hdrs and post the two requests (HEAD +
> GET) then we
> will get a much clearer picture of what is going on.
>
> Regards
> Henrik
>
Received on Fri Nov 14 2003 - 17:13:07 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:21:19 MST