The self-hosted gateway now strips detail from upstream errors before handing them back.
What's wrong with this entry?
The 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.
- Status-to-type mapping gained 413 request_too_large and 501 not_supported.
- Model names appearing in operator-facing errors are stripped of non-printable characters and truncated to 128 characters.
- Only reached on the gateway request path for customer-routed inference.
upstream error
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway
-
v2.1.229
Gateway streaming keeps connections alive with pings
Both mention gateway
-
v2.1.232
Cloud gateway sign-in explains its restart, and refuses when it cannot
Both mention gateway