Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 23:30 UTC
docs(changelog): proxy execute same-domain enforcement (#3272)
# Description Adds a public-facing changelog entry announcing the proxy execute same-domain enforcement shipped in [hermes#9582](https://github.com/ComposioHQ/hermes/pull/9582). The entry explains: - `POST /api/v3/tools/execute/proxy` now rejects absolute `endpoint` URLs whose registrable domain (eTLD+1) does not match the connection's `base_url` (HTTP `400 OriginMismatch`). - Cross-subdomain on the same registrable domain still works (e.g. `gmail.googleapis.com` ↔ `www.googleapis.com`). - Relative endpoints are unaffected. - Requests with neither `connected_account_id` nor `custom_connection_data` now return `400 MissingAuthContext`. Includes allowed vs. rejected curl/JSON examples and a "what to do" section pointing users to relative endpoints or to reach out for multi-domain toolkit allowlisting. File: `docs/content/changelog/04-24-26-proxy-execute-same-domain.mdx` # How did I test this PR - Verified the file follows the changelog conventions in `docs/.claude/guides/changelog.md`: - `MM-DD-YY-suffix.mdx` filename, `title` + `date` (YYYY-MM-DD) frontmatter, no `#` heading, `###` for sections, no emojis. - Matched the style of recent proxy/security entries (`12-30-25-proxy-binary-data.mdx`, `04-23-26-file-upload-security.mdx`). - Docs-only change — no code or type-check surface affected. Full `bun run build` validates TS code blocks only; no TS code blocks in this entry, so it is a no-op there. Triggered by: sarthak@composio.dev
No changes.