502 Bad Gateway Error

Is there a way to chase down a 502 Bad Gateway error? I have a customer
who can't access my site because of a 502 Bad Gateway Error. I doubt I
can do anything about it, but at least it would show the customer that I
tried.

Is this something that would show up in a traceroute? Even if I found
where it was coming from, is there anything I can do about it?

Hi Scott -

On Wed, 25 Oct 2006 14:10:31 -0600, Scott Bryce
<sbryce RemoveThis @scottbryce.com> wrote:

>Is there a way to chase down a 502 Bad Gateway error? I have a customer
>who can't access my site because of a 502 Bad Gateway Error. I doubt I
>can do anything about it, but at least it would show the customer that I
>tried.
>
>Is this something that would show up in a traceroute? Even if I found
>where it was coming from, is there anything I can do about it?

From RFC2616:

10.5.3 502 Bad Gateway

The server, while acting as a gateway or proxy, received an invalid
response from the upstream server it accessed in attempting to
fulfill the request.

From this it appears that it has nothing to do with routing gateways,
so traceroute is in applicable.

Does your server communicate with some other server such that it is
acting as an HTTP gateway/proxy to the other server?

If not, I suspect that the customer's ISP has some kind of HTTP
gateway/proxy system that is busted.

If the customer has a proxy configured within their browser, they
should remove it or configure it so that your site bypasses it. If
it's a transparent proxy, the ISP is the only one who can do anything.

--
Ken
http://www.kensims.net/