Repository navigation
Conversation
…_type and size
Dick, 2026-09-28: "call-log sends bodies IF SMALL." MAX_BODY_BYTES = 8 KB,
measured on the body's UTF-8 text. Over it the body is not logged and the
part carries `content_type` and `size` instead — the shape the record
already uses for a body it does not show, which the monitor renders as
"Body not logged: application/json, N bytes." No body at all is neither
field. A stated Content-Length over the limit is not read.
The caller's request body gets the same rule (`{ size }`). The 30 KB record
cap stays as the backstop.
Fleet data, last three days: every protocol body is under 2 KB (largest:
access /token request with the R3 document, 1.7 KB); senzing results under
2 KB; secret.agent.coop JWE messages 6.5 KB. The one body over 8 KB is
registry GET /resources, 27.7 KB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YTSrtvfcNAxTc5KGxr4aKh
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
1 participant
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.
Stacked on #32. Step 3 of
aauth-dev/monitorplan/CALL_LOG_PLAN.md: Dick decided 2026-09-28 "call-log sends bodies IF SMALL"; this picks the threshold and the replacement.MAX_BODY_BYTES, exported), measured on the body's UTF-8 text.body; the part carriescontent_typeandsize(bytes). That is the shape the record already uses for a body it does not show, and the monitor already renders it: "Body not logged: application/json, N bytes." No body at all has neither field, so a reader can tell the two apart.Content-Lengthover the limit is not read. Without one, the text is read and measured.init.bodystring) gets the same rule and becomes{ size }.cap,truncated: true) stays as the backstop.Why 8 KB, from Freezer (prod fleet + beta Wallet, last three days): every protocol body is under 2 KB (largest: access
/tokenrequest carrying the R3 document, 1.7 KB); senzing results under 2 KB; secret.agent.coop JWE messages 6.5 KB. The one body over 8 KB is registryGET /resourcesat 27.7 KB. Two bodies at the limit plus envelope still fit the 30 KB cap.Version 0.1.3. If #32 and this merge before a release, the release publishes 0.1.3 only.
npm test: all pass; both new tests fail on the old code.🤖 Generated with Claude Code
https://claude.ai/code/session_01YTSrtvfcNAxTc5KGxr4aKh