Proxy Error When Trying To Access Skoogle Inbox

[youravinalarrrf]

Now getting this using XP Home & IE7 - was OK earlier today. Refreshing page does not cure it. Anybody else getting the same?

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /amserver/SSORedirect/metaAlias/sky.

Reason: Error reading from remote server
--------------------------------------------------------------------------------
IBM_HTTP_Server Server at id.sky.com Port 80

Continual refreshing IE eventually states
Most likely causes:
The website is under maintenance.
The website has a programming error.

No real surprise there then!

[Keiran2K8]

I have been getting this error recently, Refreshing it sorts it out (or has done for me).

[youravinalarrrf]

NOW RESOLVED

For anyone else who comes across this problem I just cleared all IE7 browsing history and cookies etc. and it seems to have cured the problem straight away.

Here's the guff I found relating to the problem.

HTTP Error 502 - Bad gateway
Introduction
A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.

This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.

502 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '502'.

Resolving 502 errors - general
This problem is due to poor IP communication between back-end computers, possibly including the Web server at the site you are trying to visit. Before analysing this problem, you should clear your browser cache completely.

If you are surfing the Web and see this problem for all Web sites you try to visit, then either 1) your ISP has a major equipment failure/overload or 2) there is something wrong with your internal Internet connection e.g. your firewall is not functioning correctly. In the first case, only your ISP can help you. In the second case, you need to fix whatever it is that is preventing you reaching the Internet.

If you get this problem for only some of the Web sites you try to visit then it is likely to be a problem at those sites i.e. one of their pieces of equipment is failing/overloaded. Contact the people at those sites.

Resolving 502 errors - CheckUpDown
Use of proxies and caching is increasing on the Web. Our CheckUpDown robot will always try to 'drill through' to the real computer that actually hosts your Web site, but we do not have complete control over where our HTTP request actually ends up. If only one link in the chain of computers dealing with our HTTP request is broken, then an error such as 502 can easily occur.