Bad responses from proxies and gateways now name the intermediary instead of a generic error.
What's wrong with this entry?
An empty or malformed API response now raises a dedicated error that names what the body actually was and points at intermediaries between you and the API. It recognises common gateways (litellm, helicone, portkey, cloudflare-ai-gateway, kong, braintrust), Databricks hosts, reverse proxies identified by their Server: header (cloudflare, envoy, nginx, apigee, akamai, zscaler and others), and Apigee fault codes, and preserves hop headers in the report. Live on this build with no flag.
- One diagnosed case is a non-streaming request answered with an event stream, which is called out by name.
body is an event stream (the non-streaming request was answered with a stream)
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.228
API rejections are classified from a structured marker instead of prose alone
Both mention error
-
v2.1.228
Oversized media in a request is now its own rejection class
Both mention error
-
v2.1.229
Render errors are now reported instead of silently blanking
Both mention error