RE: [squid-users] Unable to access support.microsoft.com
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:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:12 PM To: Thompson, Scott (WA) Cc: Amos Jeffries; squid-users@squid-cache.org Subject: RE: [squid-users] 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:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 10:37 AM To: Thompson, Scott (WA) Cc: squid-users@squid-cache.org Subject: Re: [squid-users] 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
RE: [squid-users] Unable to access support.microsoft.com
Thx Dean and to Michael In Firefox all I get is a blank page, no errors whatsoever In IE I turned off the HTTP 1.1 settings and low and behold it works fine No other subnet is bypassing the proxy, all subnets must go thru the proxy for internet access If I change the settings in Firefox I still don't get anything just a blank page Cheers, Scott -Original Message- From: Dean Weimer [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 8:25 PM To: Thompson, Scott (WA) Cc: squid-users@squid-cache.org Subject: RE: [squid-users] Unable to access support.microsoft.com 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:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:12 PM To: Thompson, Scott (WA) Cc: Amos Jeffries; squid-users@squid-cache.org Subject: RE: [squid-users] 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:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 10:37 AM To: Thompson, Scott (WA) Cc: squid-users@squid-cache.org Subject: Re: [squid-users] 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 No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 269.23.16/1431 - Release Date: 13/05/2008 7:55 PM
Re: [squid-users] 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
RE: [squid-users] 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 -Original Message- From: Amos Jeffries [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 10:37 AM To: Thompson, Scott (WA) Cc: squid-users@squid-cache.org Subject: Re: [squid-users] 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
RE: [squid-users] 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:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 10:37 AM To: Thompson, Scott (WA) Cc: squid-users@squid-cache.org Subject: Re: [squid-users] 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
Re: [squid-users] Unable to Access support.microsoft.com through Squid
Has anyone else ran into this issue, and found a solution to the problem? I do # Fix broken sites by removing Accept-Encoding header acl broken dstdomain support.microsoft.com acl broken dstdomain .digitalspy.co.uk header_access Accept-Encoding deny broken The problem is that sending Accept-Encoding causes these sites to reply with a header that it's not supposed to (Transfer-Encoding: chunked) Cheers, Mick
RE: [squid-users] Unable to Access support.microsoft.com through Squid
Thanks for your help Mick, this solved the problem. Also after seeing this I was able to figure out that in squid 3.0 you can use request_header_access in place of header_access. Thanks, Dean Weimer Network Administrator Orscheln Management Co -Original Message- From: Michael Graham [mailto:[EMAIL PROTECTED] Sent: Friday, May 02, 2008 10:37 AM To: squid-users@squid-cache.org Subject: Re: [squid-users] Unable to Access support.microsoft.com through Squid Has anyone else ran into this issue, and found a solution to the problem? I do # Fix broken sites by removing Accept-Encoding header acl broken dstdomain support.microsoft.com acl broken dstdomain .digitalspy.co.uk header_access Accept-Encoding deny broken The problem is that sending Accept-Encoding causes these sites to reply with a header that it's not supposed to (Transfer-Encoding: chunked) Cheers, Mick
