Fix WebSocket limit for large agent messages #45

Merged

steve merged 1 commits from fix-issue-44-websocket-read-limit into main 2026-08-22 10:48:32 +01:00

Conversation 0 Commits 1 Files Changed 5

+128

steve commented 2026-08-22 10:46:02 +01:00

Owner

Copy Link

Copy Source

Summary

• define an explicit 8 MiB bound for agent/server WebSocket envelopes
• apply the same read limit on both server and agent connections
• verify payloads above coder/websocket’s 32 KiB default are accepted in both directions
• verify a large snapshots.report reaches the server projection

The limit remains bounded to protect both peers from unbounded allocation. Chunking very large projections/log events remains a separate future hardening option.

Verification

• go test ./...
• go vet ./...
• git diff --check

Fixes #44

## Summary - define an explicit 8 MiB bound for agent/server WebSocket envelopes - apply the same read limit on both server and agent connections - verify payloads above coder/websocket’s 32 KiB default are accepted in both directions - verify a large snapshots.report reaches the server projection The limit remains bounded to protect both peers from unbounded allocation. Chunking very large projections/log events remains a separate future hardening option. ## Verification - go test ./... - go vet ./... - git diff --check Fixes #44

steve added 1 commit 2026-08-22 10:46:02 +01:00

fix(ws): raise bounded agent message limit 74cb7f660f

steve merged commit 8ddd3456e1 into main 2026-08-22 10:48:32 +01:00

steve deleted branch fix-issue-44-websocket-read-limit 2026-08-22 10:48:32 +01:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

enhancement

New feature or improvement to existing functionality

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

steve

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: steve/restic-manager#45