Re: incomplete loads

Tilman Schmidt wrote:

> access.log
>
> 940604339.776 8767 HeartOfGold.sema.de TCP_MISS/000 19164 GET http://www.sommerfeldt.com/screen.jpg - FIRST_PARENT_MISS/www-cache.xlink.net -
> 940604351.801 90 HeartOfGold.sema.de TCP_IMS_HIT/304 196 GET http://www.sommerfeldt.com/screen.jpg - NONE/- image/jpeg
> 940604372.938 11753 HeartOfGold.sema.de TCP_MISS/200 30465 GET http://www.sommerfeldt.com/screen.jpg - TIMEOUT_FIRST_PARENT_MISS/www-cache.xlink.net image/jpe
>
> store.log
>
> 940604339.934 SWAPOUT 00009085 200 940604332 934832385 -1 image/jpeg 20550/20550 GET http://www.sommerfeldt.com/screen.jpg
> 940604351.801 RELEASE FFFFFFFF 304 940604332 934832385 -1 image/jpeg -1/0 GET http://www.sommerfeldt.com/screen.jpg
> 940604372.938 SWAPOUT 00009086 200 940603980 939763524 -1 image/jpeg 30111/30111 GET http://www.sommerfeldt.com/screen.jpg
>
> cache.log

Hmm.. it looks like the first request was aborted by the client when
Squid had sent 19164 bytes to it and then the download finished,
reaching 20550 bytes (see your quick_abort_* settings). This is based on
the fact that access.log does not contain HTTP status 200, and the reply
size reported there is smaller than the content length reported in
swap.log, and the fact that there was a SWAPOUT entry.

A very vierd thing is that it seems the object got replaced by another
(much newer) one when you made your full reload, and the origin servers
clock moved backwards..

Request 1: Content-length 20550 bytes, server date Oct 22 14:58:52, last
modified Aug 16 19:39:45.

Request 2: IMS_HIT. Origin server not contacted. Does not look like you
used the reload button, or you are using Internet Explorer and a network
transparent proxy..

Request 3: Content-Length 30111 bytes, server date Oct 22 14:53:00, last
modified Oct 12 21:25:24.

--
Henrik Nordstrom
Squid hacker