[ARCHIVED] Benchmark issue 491 - #491
Conversation
Add a "Secure HTTP clients" subsection under "Go code" documenting required security properties for outbound HTTP clients. Points agents to the SSRF-hardened fetch package (internal/fetch/) and lists the mandatory protections when a custom client is needed: HTTPS-only, DNS pre-resolution with IP validation via netutil, IP-pinned DialContext, redirect blocking, explicit timeout, and response size limiting. Prohibits http.Get and http.DefaultClient for external URLs from configuration or user input. Closes #376
- Add Transport.Proxy bullet to custom-client checklist (proxy omission) - Fix bold formatting to use label-colon pattern for consistency Addresses review feedback on #421
|
/fs-review |
|
🤖 Finished Review · ✅ Success · Started 10:22 AM UTC · Completed 10:29 AM UTC |
Review — approveReviewed: SummaryClean, well-scoped documentation PR that adds SSRF-hardening guidance for Go HTTP clients to Verification details
ScopeMatches issue #490 authorization. Placement under FindingsNo findings at or above the severity threshold. Reviewed with fullsend-ai 🤖
Previous runReview — ApprovePR: #491 — Add AGENTS.md guidance for secure HTTP client construction in Go SummaryThis PR adds a well-scoped "Secure HTTP clients" subsection under the Go code section of AGENTS.md, documenting required security properties for HTTP clients that fetch external URLs. The change traces directly to issue #490 (a retro-action from PR fullsend-ai#3002 where review agents caught missing SSRF protections). FindingsNo blocking findings. Verified claims against codebase:
Dimensions reviewed
Labels: PR adds developer guidance documentation for secure HTTP client patterns |
|
🤖 Finished Review · ✅ Success · Started 10:30 AM UTC · Completed 10:36 AM UTC |
Closes #490
LSP experiment v2: clean first-review with gopls-lsp enabled.
Code identical to PR #421 (issue #376).
Branch created from commit 8d10b3b.