{"version":"2.1.228","anchor":"gateway-strips-detail-out-of-upstream-errors-before-returnin","canonical_anchor":"gateway-strips-detail-out-of-upstream-errors-before-returnin","heading":"Gateway strips detail out of upstream errors before returning them","tier":"notice","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-strips-detail-out-of-upstream-errors-before-returnin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway strips detail out of upstream errors before returning them\n\nThe self-hosted gateway now strips detail from upstream errors before handing them back.\n\n**What**\n\nThe self-hosted gateway no longer passes upstream error bodies through as-is. It drops the `anthropic-organization-id` header, reads at most 64KB of the body, keeps only error types on a fixed allowlist, and substitutes a generic message. A small set of gateway headers is forwarded, and `retry-after` survives on 429s.\n\n**Details**\n\n- Status-to-type mapping gained 413 request_too_large and 501 not_supported.\n- Model names appearing in operator-facing errors are stripped of non-printable characters and truncated to 128 characters.\n- Only reached on the gateway request path for customer-routed inference.\n\n**Evidence**\n\n`upstream error`\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}