On Sat, 15 Jul 2023, Paul Fotheringham via curl-library wrote:
bytesleft == 0 means no more data in this frame.
bytesleft == 0 and CURLWS_CONT bit is not set means the end of the message.
Unfortunately that does not seem to be the case for me. I fragment my
message into eight frames and the first frame does not have the CURLWS_CONT
bit set, the following seven frames do.
It might be a bug then? I read this as you saying that libcurl delivers these
eight frames as 8 whole fragments so that bytesleft is zero in all of them?
See
https://github.com/curl/curl/blob/a70d97c46cdf94ef8adf9ed6cb0af01c2aea038b/lib/ws.c#L428-L447
This is what I would expect if CURLWS_CONT has the same meaning as the
continuation frame opcode.
That's the intention.
Can you provide an example snippet that reproduces 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/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
