for web usage. We noticed that when using Squid it would load up all the
> items of a web page (which may take a while to do) and then give them to our
Squid 2 certainly doesn't do this. At a guess the browser was
orignally creating large numbers of connections, one for each image,
and therefore frustrating connection caching, but squid is
implementing the connection caching properly with the result that the
browser doesn't get all the image sizes until late. If the page is
formatted using tables, and the sizes of the cells aren't available
on the first pass, some browsers will not render the table until they
know all the sizes, which will, at least, require seeing the graphic
file headers of all the images.
If this is the case, the proper fix is to provide size information in
the top level HTML.
> network user. When we browse off the network without using Squid items are
> displayed on our brower as soon as they are received off the Net. Does
> anyone know of a way to change or improve this within Squid? The latency we
> are currently experiencing after the HTTP request is unbearable.
-- David Woolley - Office: David Woolley <djw@bts.co.uk> BTS Home: <david@djwhome.demon.co.uk> Wallington TQ 2887 6421 England 51 21' 44" N, 00 09' 01" W (WGS 84)Received on Tue Feb 16 1999 - 07:44:37 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:44:34 MST