On Wed, Feb 20, 2008, Shoebottom, Bryan wrote: > Adrian, > > Thank you for the suggestions, the problem is with timestamping and > window scaling. When I disable both of these, the site works. Now I am > debating whether I should do this or have this single site bypass the > cache entirely. > Disabling timestamping looks like it's no big deal, but disabling window > scaling looks like it stops TCP negotiation of window sizes larger then > 64K. I am looking at this as a big negative, but would appreciate your > thoughts as you are more experienced with caching technology. > Its unfortunate, but this is the sort of thing which needs to be done on various internet-connected services. The problem is that the Window Scaling stuff can be "slightly off" and still work mostly OK, and this confuses debugging by "does it work or not" methods (ie, does the user complain.) You could try setting the scaling factor to 2. Ideally some logic could be put into Squid to identify when a connection fails/ angs and retry that peer with window scaling/timestamps/pmtu disabled, flagging that peer/network as "busted". adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
