Re: Incorrect content length

I'm still trying to get some definitive data on this. First (and second)
impressions are that the content-length isn't checked against the
document until it decides whether it is going to actually move it from
RAM to disk.

I could be very wrong here. Things have been stressfully busy, and I've
had my mind on many other things...but that's the way it _looked_.

Certainly, the simple test I did with it: Fetch an object. Deliberately
break it with a deft finger on the modem power-switch. Reconnect and
fetch it again. Squid cheerfully returns the partial object. Shut squid
down and start it up again to clear the RAM cache. On the next request,
squid fetches the whole object again.

D

Henrik Nordstrom wrote:
>
> Dancer wrote:
>
> > I'm looking at some broken objects now, and wondering why they were
> > TCP_HITs, when I figure the cache should have discarded them as
> > incomplete.
>
> Squid should not cache objects with the wrong content length. There is
> however some servers that don't send a content-length header....
>
> ---
> Henrik Nordström
> Sparetime Squid Hacker

-- 
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.