Whirlpool

Can anybody get to support.microsoft.com ?

Yep, its working for me.

Still not so sure about its new Layout though.

In Melboune, I just get a black page in either IE7 or Firefox and at home (Bigpond) and at work (Pacnet)

hmmm. If I bypass squid proxy server it works.

Thanks,
Andrew.

Andrew writes...

If I bypass squid proxy server it works.

Ooohhh, same here.

Via squid - blank page.
Direct - works perfectly.

!

SquidNT 2.5 Stable11, FireFox 2.0.14.

edit: However IE7 (and IETab) works fine via both Squid & direct. Hmmm.

Same here. The problem seems to be related to the handling of the "Accept-Encoding" header sent from the browser.

A work-around that I have put in place is to add the following to the squid server's config:

# Fix support.microsoft.com by removing Accept-Encoding header
acl support.microsoft.com dstdomain support.microsoft.com
header_access Accept-Encoding deny support.microsoft.com

You can also try to remove the tick from "Use HTTP1.1 through proxy connections" in IE's Advanced internet options tab, although this might break some other web pages.

That fixed it for me too.

It was on my todo list for today.

Thanks.

Thanks for the information - it works a treat. Interesting if you are using multiple levels of squid proxies, the config fix is only required on just one server.

It's working fine for me

Thanks HWK, much appreciated :)

The grumbles about this were just starting to filter in here from the desktop support dept.

Interesting side note - my install of IE6 was still functioning through squid (but yeah IE7 and FF were both boned).

LOL, maybe a sales rep for MS Proxy had told someone important that Squid would break their Updates and then got the website admins to make sure that was actually true before someone called BS on him :P

Nice catch with Squid - fixed one of our guys problem with the Dark Side's website (Hi Gus). :-)

Interestingly Konqueror (the KDE browser) worked quite happily with it..

This one contrary site was getting in the way of us wanting to fully enable HTTP/1.1 on our corporate desktop fleet to fix an incompatibility with external sites that gzip their cascading style sheets, so we logged a call & got MS to fix their site.

Were we the first on the planet to do so? :D

The MS developers traced it back to "a misconfigured setting."
After an initial falter where the corrections didn't replicate out to all their servers it seems the site is now working fine; HTTP/1.1 or no, SQUID or no. I wonder if this has spread to the rest of the world yet. Anyone further afield than Australia confirm this?

Before today (since ~April 18?) when we had HTTP/1.1 enabled through proxy connections we were getting HTTP/1.0 responses coming back from Microsoft's IIS but with chunked encoding tags (which are part of the 1.1 specification, not 1.0) = befuddled browsers.

I can get to the support.microsoft.com site, but for about 3 days, I'm trying to just post a question on the Windows Media Player site, but something appears to be messed up on their side......because even when I've logged in, and select the option for posting a question...... I find that nothing works there.

http://www.microsoft.com/windows/windowsmedia/community/newsgroups/WindowsMedia/default.mspx?dg=microsoft.public.windowsmedia.player&lang=en&cr=US

And microsoft has the typical customer fence to keep the customers out.....to stop customers from getting in touch with MS by any 'convenient' means (for finding out what the problem is). That's what happens when a company gets too large and making too many profits......the small customer means nothing to them.

If u mean it just refreshes the list of postings instead of opening a posting form, ya, same here. However, I believe u'r off-topic from this support.microsoft.com vs squid vs http/1.1 discussion thread. :o}

Ninja Duck writes...

If u mean it just refreshes the list of postings instead of opening a posting form, ya, same here.

Thanks for letting me know that you found the same thing ninja. I just posted because I thought that it might have been related to something broken on the MS sites. Thanks again for confirming the issue that I came across.