@DownPW it’s your only realistic option at this stage.
error with v3 in browser console
-
Hello @mark
I have several disconeexion on v3.2.3 with socket error, csrf; error 400
with this on console :
an idea ?
-
@DownPW Yes. Error
400
is bad request error which stems from thesocket.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
-
hmmm must will test for error 400
And what do you think about websocket wss error transport ?
-
@DownPW it’s in relation to the response I provided above
-
-
Did this solution help you?
Related Topics
-
NodeBB socket with CloudFlare
Unsolved Performance -
-
-
-
-
-
-
Invalid CSRF on dev install
Moved Solved Tips