Thanks Henrik, but no joy when the suggeted code is added to the conf file. I agree that the site is broken but since I am sure there will be others, I need a workaround. Anything else you can think of? Thanks, Dave
-----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Thursday, December 28, 2006 6:42 PM To: Dave Rhodes Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Yet Another "Can't Open Website" tor 2006-12-28 klockan 14:09 -0500 skrev Dave Rhodes: > I have a problem opening www.specialized.com using squid 2.6 Stable5 on > SUSE 10.1 X86-64 on an HP DL320 3.2GHz with 4GB RAM and 100GB HDD (RAID > 10). The squid config is fairly vanilla as the server is in it's > infancy (as am I to squid). After some fairly extensive testing and > searching (FAQs, google, this list, etc.) it appears that the site may > require an HTTP/1.1 function that squid does not yet support. I'd like > to, first of all, verify that with this group and 2nd, if not, see if > anyone has any suggestions. The site is broken and responds with chunked encoding in response to HTTP/1.0 requests (a MUST NOT requirement in the HTTP specifications). Most likely works if you drop the Accept-Encoding header. acl broken_sites .specialized.com header_access deny Accept-Encoding deny broken_sites Regards Henrik
