Repository navigation
A body refused for its size says the largest the endpoint takes, and a service that forwards a command takes none it cannot forward - #113
Closed
riccardone wants to merge 1 commit into
Closed
riccardone wants to merge 1 commit into
riccardone wants to merge 1 commit into
Conversation
…a service that forwards a command takes none it cannot forward Entry 40 of #37. A body too large is 413, with nothing in the refusal a client can act on, and a service that forwards commands may accept one the next hop refuses. best-peer's 413 carries details.limit_bytes, and a workspace's door takes 4 KiB less than the root so a forwarded command always fits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Entry 40 on #37 (#37), proven by best-peer.
Why
Input Limits has a body too large answered
413, and nothing in the refusal tells the client what would fit, so it cannot correct itself; a body over the limit is refused before it is read, so no field can be named either. A service that forwards a command to another service, in an envelope of its own, can accept one the next hop then refuses after the first said201. best-peer's413carriesdetails.limit_bytes, the most the door that refused takes, and its message names it; a workspace's door takes 4 KiB less than the root, so a command its cloud passes on to a member is never refused there.What
Input Limits in
specs/security.md:details.limit_byteson a413, and a forwarding service takes no body it cannot forward whole.Left out of the entry: whether a schema version may gain bounds in place, as best-peer's
1.0documents did. That is a versioning question for the owner, not a sentence this PR settles.No version bump and no release notes here: the PRs from #37 do not collide that way, and the release that gathers them does both.
🤖 Generated with Claude Code