Scott, If you want to test this without modifying your proxy configuration you can uncheck the http 1.1 options on the Internet Explorer Options Advanced tab. Also does it work through Firefox or another browser? Firefox reports a content encoding error when accessing support.microsooft.com when this problem is present. If these steps show that this is indeed the problem you probably need to discover why your other subnets are working, are they in fact bypassing the proxy? Thanks, Dean Weimer Network Administrator Orscheln Management Co -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: Tuesday, May 13, 2008 11:12 PM To: Thompson, Scott (WA) Cc: Amos Jeffries; squid-users@xxxxxxxxxxxxxxx Subject: RE: Unable to access support.microsoft.com > Thx Amos, but why would it work from every other subnet but the one I am > on? > They all go out the same proxy server > > Scott Could be the other causes entirely. Thats just the most common one seen with support.microsoft.com recently. - TCP-level stuff like windoss scaling, ECN, PMTU discovery come in second place and produce similar errors. - configuration loops (302's) may have a similar effect. The biggest clue is the exact content of the error page. A squid-generate page you can at least track through the cache.log. If it's one of the IE-generated ones then it's probably a low-level issue with IE either handling the page info or connecting to squid. Amos > > -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Wednesday, 14 May 2008 10:37 AM > To: Thompson, Scott (WA) > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Unable to access support.microsoft.com > >> >> Hi all >> A strange one and probably something stupid at my end but for some >> reason I cannot access support.microsoft.com >> In IE all I get is a 'cannot display the webpage' error, nothing from >> Squid to indicate an error. > > support.microsoft.com have a broken HTTP/1.1 server. > > Squid 3.0, 2.5, or an early 2.6? > 2.x - Upgrade to a more recent release. > 3.x - A header hack to your config is available to bypass this. > > # Fix broken sites by removing Accept-Encoding header > acl broken dstdomain ... > request_header_access Accept-Encoding deny broken > # NP: don't forget to remove it again when you upgrade out of 3.0 > > For all the guff see > http://squidproxy.wordpress.com/2008/04/29/chunked-decoding/ > > Amos > > >
