Re: incomplete loads

Tilman Schmidt wrote:

> and I am rather frequently seeing files being incompletely loaded - ie. HTML
> pages breaking of in mid-text or images showing only the top part.

That's not nice at all.

> A simple browser reload only shows the same incomplete info again, but shift/reload
> in most cases gets the complete info.

Quite normal on such errors regarless of how they are caused. The
browser incorrecly thinks it has the whole page, and a plain reload only
verifies that the page hasn't been modified which it hasn't.

> 940509416.770 41246 HeartOfGold.sema.de TCP_MISS/200 27312 GET http://news.cis.dfn.de/de/hierarchies.html - FIRST_PARENT_MISS/www-cache.xlink.net text/html
> 940511646.728 133775 HeartOfGold.sema.de TCP_MISS/200 27203 GET http://news.cis.dfn.de/de/hierarchies.html - PARENT_HIT/www-cache.xlink.net text/html

Hmm.. it looks like you got the whole page on both requests. The odd
thing is that the reply of the first (failing) request was 109 bytes
larger than the second (not failing)..

It would be interesting to see the store.log entries for these requests.

> The portion of cache.log around that time shows:
>
> 1999/10/21 14:17:17| Detected DEAD Parent: www-cache.xlink.net/3128/3130
> 1999/10/21 14:17:18| Detected REVIVED Parent: www-cache.xlink.net/3128/3130
> 1999/10/21 14:28:01| TCP connection to www-cache.xlink.net/3128 failed

Your parent seems to have servere performance problems. It is not
answering ICP queries in a timely manner and also sporadically refusing
TCP connections on the proxy port.

--
Henrik Nordstrom
Squid hacker