mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
a6c1d12206
Add a constructed PCAP where the HTTP/websocket server send a WebSocket ping message directly with the packet of the HTTP reply. Ensure this is interpreted the same as if the WebSocket message is in a separate packet following the HTTP reply. For the server side this should work, for the client side we'd need to synchronize suspend parsing the client side as we currently cannot quite know whether it's a pipelined HTTP request following, or upgraded protocol data and we don't have "suspend parsing" functionality here. |
||
|---|---|---|
| .. | ||
| broker-websocket.zeek | ||
| coalesced-reply-ping.zeek | ||
| events.zeek | ||
| jupyter-websocket.zeek | ||
| wstunnel-http.zeek | ||
| wstunnel-https.zeek | ||
| wstunnel-ssh-configure-wrong.zeek | ||
| wstunnel-ssh-configure.zeek | ||
| wstunnel-ssh.zeek | ||