@devries-cameron20 / composio Mirror · read-only / commits / 8bd3044fb
Fork 0

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): add Before/After migration block for proxy same-domain

Per the changelog guide's breaking-change checklist, add a Migration section with explicit Before/After code examples so developers with existing absolute-URL calls can see the exact shape of the fix at a glance, rather than inferring it from the "What to do" bullets. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: sarthak <sarthak@composio.dev>

Zen Agent committed Apr 24, 2026 at 06:49 UTC 8bd3044fb1a366ec3d5641189dfe2a35106ddaf2
1 file changed +36
docs/content/changelog/04-24-26-proxy-execute-same-domain.mdx
+36
@@ -14,6 +14,42 @@ Cross-subdomain requests on the same registrable domain continue to work — for
14 Existing proxy calls that pass an absolute `endpoint` URL whose registrable domain does not match the connection's `base_url` will now fail with `400 OriginMismatch` instead of being forwarded. Calls that omit both `connected_account_id` and `custom_connection_data` will fail with `400 MissingAuthContext` instead of being forwarded without auth.
15 </Callout>
16
17 +### Migration
18 +
19 +If you currently pass an absolute URL that points at a different domain than your connection's `base_url`, switch to a relative endpoint (resolved against `base_url`) or an absolute URL under the same registrable domain.
20 +
21 +**Before** — absolute URL on a different domain (will be rejected):
22 +
23 +```json
24 +{
25 + "endpoint": "https://api.someservice.com/v1/items",
26 + "method": "GET",
27 + "connected_account_id": "ca_..."
28 +}
29 +```
30 +
31 +**After** — relative endpoint (recommended):
32 +
33 +```json
34 +{
35 + "endpoint": "/v1/items",
36 + "method": "GET",
37 + "connected_account_id": "ca_..."
38 +}
39 +```
40 +
41 +**Or** — absolute URL on the same registrable domain as the connection's `base_url`:
42 +
43 +```json
44 +{
45 + "endpoint": "https://uploads.someservice.com/v1/items",
46 + "method": "GET",
47 + "connected_account_id": "ca_..."
48 +}
49 +```
50 +
51 +If your integration legitimately needs to call a different registrable domain for the same connection, reach out so we can add the additional host to the toolkit allowlist.
52 +
53 ### What changed
54
55 - Absolute `endpoint` URLs on a different registrable domain than the connection's `base_url` are rejected with HTTP `400 OriginMismatch`. The upstream request is never made.