Open conan13101998 opened 1 year ago
Hi! You are right, we need to take in account the maxPayload
field sent by the server, like the JS client: https://github.com/socketio/engine.io-client/commit/46fdc2f0ed352b454614247406689edc9d908927 (added in version 4.5.0)
So is there a way we can send a big payload now or will your fix be released in the near future?
The problem here is that when the client is using HTTP long-polling, the packets are concatenated and the total size is over the maxHttpBufferSize
limit of the server.
So as a workaround you can either:
maxHttpBufferSize
limit of the serverI have tried all methods you said:
maxHttpBufferSize
: in server i configured maxHttpBufferSize
to 1e8 ~ 100MB, it's much more bigger than 32MB but why i still faced the transport close
erroroptions.transport = new String[]{"websocket"}
in java client but no change in result. Still transport close
i have same problem but im using java server. have you found any solution ?
@conan13101998 were you able to figure out any solution for this?
Describe the bug When i try to send message to NodeJS Socket.io Server, small message (< 32MB) is succeed but when payload more than 32MB =>
disconnect
event fired with reasontransport close
. Sometime it send 1st big message succeed and another fail because timeout (client auto reconnect after disconnected)Note: I also implemented ACK in both server and client
To Reproduce
Socket.IO server version:
4.5.2
with ExpressServer
Socket.IO java client version:
2.1.0
Client