You're figuring wrong. ;-)
Squid does not wait until an object is fully cached before beginning to
send it to the client, and it also has no conception of a "web page".
It fetches what the browser asks it to, when it asks it to. Is this
behavior specific to one particular page and/or browser?
Did you check to be sure DNS resolution is fast using the cache manager
as I suggested? (This may not be the problem you're seeing, but it is
the first thing to check.)
Kay Joplin wrote:
> i checked the DNS settings and they seem to be alright. the way i figure, is
> the page gets downloaded to the squid cache first before it appears on
> screen. it usually takes a while before the page actually pops up on my
> screen and when it does, it pops up entirely. for the impatient this can be
> quite frustrating, since we don't always want to wait for everything to
> download nicely before getting the chance to browse to more important
> information. i am not aware that this could be a something the designer of
> the page implemented into the page for one reason or another.
-- Joe Cooper <joe@swelltech.com> Web caching appliances and support. http://www.swelltech.comReceived on Sat Jun 08 2002 - 07:47:19 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:36 MST