I have been seeing this since a while, but whenever I load a page on stackoverflow.com or meta.stackoverflow.com I see Unexpected response code: 502 in the console on Chrome.

It is innocuous for me, but I am guessing that these 502's are the result of extraneous calls which must add some server strain.

Update: seems that the WebSockets are to blame. From the HAR:

{ "name": "Host" , "value": "sockets-se.or.stackexchange.com" },

And when I visit sockets-se.or.stackexchange.com I get

502 Bad Gateway, The server returned an invalid or incomplete response.

  • 3
    Quit straining our servers! Commented Dec 17, 2012 at 18:14
  • It's not a bug, it's a feature! Commented Dec 17, 2012 at 19:13
  • @RichardJ.RossIII may i ask how its that feature ? Commented Dec 18, 2012 at 6:41
  • You can't directly browse to web sockets host, it's giving 502 even when it's all OK. Anyway, go to the Network tab of Chrome Developer Tools and click the "sockets-se.or.stackexchange.com" entry. There should be Frames tab, what you see there? Commented Dec 20, 2012 at 20:37
  • The Status is success but the type is Pending, since the count of websocket calls is always equal to the count of 502 alerts, I assume it is not really a success ;) Also I cannot look at request header or response.
    – tomdemuyt
    Commented Dec 20, 2012 at 20:41

1 Answer 1


Response code 502 when connecting to our socket server is also dished out by some proxy servers that are not able to deal with web sockets. I have seen this happen when using a 3G mobile connection.

  • This only happens for me in one location, so that must be it.
    – tomdemuyt
    Commented Dec 31, 2012 at 14:56

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .