Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Experimental websocket API
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 29 Oct 2022 23:14:39 +0200 (CEST)
On Sat, 29 Oct 2022, Thomas Glanzmann via curl-library wrote:
>> * WS: got 1086 websocket bytes to decode
>> * WS:237 received FIN bit 1
>> * WS: received OPCODE BINARY
>> * WS: received 1024 bytes payload (0 left)
>
> It says it gets 1086 bytes of date but only receives 1024. If I understand
> correctly, the header is not that big. So somehting is strange here.
It would rather indicate that it got more than one websocket fragment in a
single read. Or that there's a bug. Or both! =)
Can you describe for me how to reproduce this?
Date: Sat, 29 Oct 2022 23:14:39 +0200 (CEST)
On Sat, 29 Oct 2022, Thomas Glanzmann via curl-library wrote:
>> * WS: got 1086 websocket bytes to decode
>> * WS:237 received FIN bit 1
>> * WS: received OPCODE BINARY
>> * WS: received 1024 bytes payload (0 left)
>
> It says it gets 1086 bytes of date but only receives 1024. If I understand
> correctly, the header is not that big. So somehting is strange here.
It would rather indicate that it got more than one websocket fragment in a
single read. Or that there's a bug. Or both! =)
Can you describe for me how to reproduce this?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-10-29