02edae54e8
- Fix a bug in EAGAIN handling when sending frames that led to a
corrupted last byte of the frame sent.
- Restore sanity to curl_ws_send() behaviour:
- Partial writes are reported as OK with the actual number of
payload bytes sent.
- CURLE_AGAIN is only returned when none of the payload bytes
(or for 0-length frames, not all of the frame header bytes)
could be sent.
- curl_ws_send() now behaves like a common send() call.
- Change 'ws-data' test client to allow concurrent send/recv
operations and vary frame sizes and repeat count.
- Add DEBUG env var CURL_WS_CHUNK_EAGAIN to simulate blocking
after a chunk of an encoded websocket frame has been sent.
- Add tests.
Prior to this change data corruption may occur when sending websocket
messages due to two bugs:
1)
|
||
|---|---|---|
| .. | ||
| .gitignore | ||
| CMakeLists.txt | ||
| h2-pausing.c | ||
| h2-serverpush.c | ||
| h2-upgrade-extreme.c | ||
| hx-download.c | ||
| hx-upload.c | ||
| Makefile.am | ||
| Makefile.inc | ||
| tls-session-reuse.c | ||
| upload-pausing.c | ||
| ws-data.c | ||
| ws-pingpong.c | ||