Change #274599

Comments

ws: pause/unpause write handling
Websocket frames need to be written individualy, so that applications
can access the frame meta data correctly. This worked until the write
function triggered a pause. Remaining frames accumulated in the "out"
writer's buffer and on unpaused were written in one chunk.

ws decode writer will now stop writing frames when the client writer
is paused. To handle the writing of buffered raw data after an unpause,
client writers have gotten a new "flush" method.

Add pytest test_20_12 with a new client to check handling of pauses
and websocket frames.

Reported-by: Hendrik Hübner
Fixes #22273
Closes #22283

Changed files

• lib/content_encoding.c
• lib/cw-out.c
• lib/cw-pause.c
• lib/cw-pause.h
• lib/ftp.c
• lib/headers.c
• lib/http_chunks.c
• lib/sendf.c
• lib/sendf.h
• lib/ws.c
• tests/http/Makefile.am
• tests/http/test_20_websockets.py
• tests/http/testenv/env.py
• tests/http/testenv/ws_4frames_server.py
• tests/libtest/Makefile.inc
• tests/libtest/cli_ws_pause.c