{"version":"2.1.299","anchor":"proxy-redirect-responses-get-a-specific-non-retry-error-mes","canonical_anchor":"proxy-redirect-responses-get-a-specific-non-retry-error-mes","heading":"Clearer error when a proxy answers with a redirect","tier":"notice","area":"Internals","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/proxy-redirect-responses-get-a-specific-non-retry-error-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Clearer error when a proxy answers with a redirect\n\nWhen a proxy answers with a redirect, Claude Code now says the redirect is not followed and that retrying will not help\n\n**What**\n\nA proxy is a server that passes your network traffic on to the internet. When a proxy answers a request with a redirect, meaning HTTP status 301, 302, 303, 307 or 308, Claude Code now says the proxy itself answered with a redirect, that it does not follow it, and that asking again will not change that. Before, every proxy rejection used the same general \"rejected the request\" message.\n\n**Why**\n\nIf you work behind a proxy, you can see why retrying is pointless and look at the proxy's setup instead.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}