For the web site that we are developing and testing, we occasionally got error 502 (Bad Gateway). It does not entirely make sense, if we truly have a proxy issue etc, we would get this all the time, but we only got it occasionally. I suspect 504 (Gateway Timeout) is probably more proper, but that’s only a guess. We turned on trace and I am hoping to find out more.

Maybe someone on this forum experienced the same issue before… Any experience to share?

My IIS does call web services that are hosted on a JBOSS server, and there are multiple security components between JBoss and IIS.

I believe that the reason that IIS threw 502 error was that occasionally web services timed out. Increased timeout value on IIS side for those web services, and will observe whether this takes away the 502 error.

We tested today with those security components turned off. One of them is a reverse proxy, and we noticed that IIS started to report timeout simply as timeout, and no longer report timeout as bad gateway. This is it.