error with v3 in browser console

[DownPW]

Hello @mark

I have several disconeexion on v3.2.3 with socket error, csrf; error 400

with this on console :

an idea ?

[phenomlab]

@DownPW Yes. Error 400 is bad request error which stems from the socket.io connection being closed before it is processed. This I’m 100% certain will be caused by Cloudflare and another reason as to why I do not use their services anymore (aside from royally screwing up Google Search on my site).

Cloudflare is effectively forcing a rate-limit on the socket connections. You can test this theory yourself by disabling Cloudflare temporarily. On the free plan, connections for sockets are first come, first served, and there is also a limited pool available.

More detail below

https://community.cloudflare.com/t/400-bad-request-when-communicating-over-socket

[DownPW]

hmmm must will test for error 400

And what do you think about websocket wss error transport ?

[phenomlab]

@DownPW it’s in relation to the response I provided above