Skip to content

fix(edge,ws): enforce WebSocket frame size cap, unbuffered WS proxy, and plain health type - #4

Merged
ATLURI0001 merged 1 commit into
mainfrom
fix/ws-frame-limit-and-edge-buffering
Nov 12, 2026
Merged

ATLURI0001 merged 1 commit into
mainfrom
fix/ws-frame-limit-and-edge-buffering

Conversation

@ATLURI0001

Copy link
Copy Markdown
Owner

Adds explicit 1 MiB max_msg_size on WebSocketResponse, disables disk temp buffering (proxy_max_temp_file_size 0) with explicit send timeout on /ws/, and sets default_type text/plain on internal health endpoint.

@ATLURI0001
ATLURI0001 merged commit 01afd95 into main Nov 12, 2026
1 check failed
@ATLURI0001
ATLURI0001 deleted the fix/ws-frame-limit-and-edge-buffering branch November 12, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant