You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
websocket: Tighten frame decoding to RFC 6455 requirements
Reject WebSocket frames that violate RFC 6455 instead of accepting them or
treating malformed input as an orderly tunneled TCP shutdown.
Require every client-to-server frame to be masked and every
server-to-client frame to be unmasked. Require control frames to be final
and limit their payloads to 125 bytes.
Validate CLOSE payload structure by rejecting one-byte payloads and
requiring the optional reason following the status-code bytes to be valid
UTF-8. Keep the status-code bytes opaque so the codec remains compatible
with future protocol revisions.
Distinguish a valid WebSocket CLOSE from termination of the underlying
transport. Treat a transport FIN received without CLOSE, as well as other
frame protocol errors, as an abort that closes both tunnel directions
immediately.
Add integration coverage showing that unmasked client frames, malformed
CLOSE payloads, and transport termination without CLOSE are rejected.
Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
0 commit comments