fix(net): cap response body reads via configurable size limit#41
Merged
fix(net): cap response body reads via configurable size limit#41
Conversation
6 tasks
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.
Summary
http.MaxBytesReaderwith a newNetworkConfig.BodySizeLimitfield (0 = unlimited;net.DefaultBodySizeLimit = 1 MiBapplied by all current callers).ResponseTruncatedonHTTPResponseandWebsiteCheckResult, and logs a warning when the cap is hit, so assertion failures against truncated bodies are traceable.math.MaxInt64clamp that works around a known overflow bug inhttp.MaxBytesReader.Replaces #38.
Test plan
go build ./...go vet ./...go test ./...(all packages pass)TestCheckWebsiteBodyLimitcovers: body under limit, body equals limit, body exceeds limit (truncation + warning),0 = unlimited, andDefaultBodySizeLimit caps at 1 MiBupdo monitoragainst a target that returns a >1 MiB response and confirm the warning fires without breaking the probe