Skip to content

fix: preserve application HTTP binding and credential boundaries - #10

Merged
anycodes merged 4 commits into
mainfrom
feat/template-workflows-20261023
Oct 23, 2026
Merged

anycodes merged 4 commits into
mainfrom
feat/template-workflows-20261023

Conversation

@anycodes

Copy link
Copy Markdown
Contributor

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

  • Validate endpoint/user information, operation paths and authority/framing headers; reject conflicting gateway/application Authorization.
  • Set manual redirect handling and refuse same-origin cross-sandbox redirects as well as foreign targets.
  • Update both README languages, changelog and owner engineering records.

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.
  • Evidence: .agents/evidence/verify/2026-10-23-bound-http-client.md.
  • Remote Node 20/22 CI and any required review must pass on the final head before merge. These checks do not certify a cloud provider or publish a package.

@anycodes
anycodes merged commit 18dc919 into main Oct 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: implement explicit template workflows without legacy compatibility

1 participant