Repository navigation
fix: preserve application HTTP binding and credential boundaries - #10
Merged
Merged
Conversation
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.
Description
Preserve the selected application HTTP binding across every request: proxy prefix and signed base query stay intact, redirects and namespace traversal are refused, gateway headers and application tokens have distinct inputs, and public endpoint/error displays omit query secrets. The Node SDK remains an HTTP application client.
Fixes #9.
Changes
Validation
npm ci,npm run typecheck,npm test: all 15 tests passed, including the real local Python server loop and new HTTP binding regressions.npm pack --dry-run,node examples/agent-loop.mjs: passed; local processes stopped..agents/evidence/verify/2026-10-23-bound-http-client.md.