{"version":"2.1.248","anchor":"clearer-error-when-a-proxy-or-gateway-returns-something-that","canonical_anchor":"clearer-error-when-a-proxy-or-gateway-returns-something-that","heading":"Clearer error when a proxy or gateway returns something that is not an API response","tier":"notice","area":"API Errors","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/clearer-error-when-a-proxy-or-gateway-returns-something-that","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Clearer error when a proxy or gateway returns something that is not an API response\n\nBad responses from proxies and gateways now name the intermediary instead of a generic error.\n\n**What**\n\nAn 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.\n\n**Details**\n\n- One diagnosed case is a non-streaming request answered with an event stream, which is called out by name.\n\n**Evidence**\n\n`body is an event stream (the non-streaming request was answered with a stream)`\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}