Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

400 Bad Request on POST

See original GitHub issue

This seems to be isolated to Windows 8.1 running Chrome 44, basically all of the POST /socket.io/?EIO=3&transport=polling&t=L7wyBG2 HTTP/1.1 always return 400 (Bad Request).

This is with socket.io 1.4.4

Issue Analytics

State:
Created 8 years ago
Comments:11 (3 by maintainers)

Top GitHub Comments

1reaction

btmdavecommented, Jan 20, 2016

Ok, so this turned out be related to pdf.js which was included on our page and was overriding xmlhttprequest prototype. I’ll close this out.

0reactions

qiuyu0112commented, Dec 20, 2019

I make http request: GET /socket.ioEIO=4&transport=websocket&t=1576482213&token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9%2EeyJhcHBfaWQiOiIxNWRmNGQzZiIsImNsaWVudCI6IndpbmRvd3MiLCJwbGF0Zm9ybSI6InZvcCIsInRpbWVzdGFtcCI6MTU3NjQ4MjIxMywiaXAiOiIxMjQuMTI4LjUuNDYiLCJ1eF90aW1lIjoxNTc2NDgyMjEzMTI1fQ%2EZ585Vd6CbrN2utmxOxIDH%2DNbCQAOROW0Zj50WVtf3PI HTTP/1.1 host: msg01-open.e.vhall.com Sec-WebSocket-Key: zH6fjF8L9iFsomPyehKlUw== Sec-WebSocket-Version: 13 User-Agent: WebSocket++/0.8.1 Connection: Keep-Alive

HTTP/1.1 400 Bad Request Content-Type: application/json Access-Control-Allow-Origin: * Date: Mon, 16 Dec 2019 07:43:37 GMT Connection: close Transfer-Encoding: chunked

22 {“code”:3,“message”:“Bad request”} 0

any helper