[Libwebsockets] Connection closed on firefox but not chrome.
sgh at sgh.dk
Fri May 10 09:59:36 CEST 2019
> The best way is hack the minimal server on master to show the same problem for you, and paste the hack patch and instructions so I can try it here. If master + hack cannot be made to fail, try your stuff on master.
> The bug claims the server starts sending trash... but lws has nothing in common with that server and relies on user code to tell it what to send.
> ws messages > 32KB are fine, with fragmentation you can send GB messages (although js cannot receive them due to memory constraints) but outside of localhost, internet connections will quickly balk at randomly being given 32K in one lump. So it may be another way of saying 'issue related to partial send handling' or 'user code doesn't observe sending rules'.
Thank you for the quick response Andy. I'll see if I can hack together
something that exposes the issue.
More information about the Libwebsockets