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 ?
PW and WS Spirit alive
-
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
400is bad request error which stems from thesocket.ioconnection 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 ?
PW and WS Spirit alive
-
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
-
undefined DownPW has marked this topic as solved on
-
undefined DownPW referenced this topic on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
