{"version":"2.1.301","anchor":"remote-settings-fetch-non-200-3xx-handling-and-no-redirect","canonical_anchor":"remote-settings-fetch-non-200-3xx-handling-and-no-redirect","heading":"Remote settings downloads from a custom address no longer retry on a redirect","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/remote-settings-fetch-non-200-3xx-handling-and-no-redirect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Remote settings downloads from a custom address no longer retry on a redirect\n\nWhen remote settings come from a custom address, a redirect response now fails at once instead of being retried, and redirect statuses are recorded\n\n**What**\n\nClaude Code can download remote settings, which an organization uses to manage it centrally. When the sign-in process supplies a custom address for those settings, Claude Code already refused to follow redirects (responses that point to a different address). It now also stops at once on such a response instead of retrying the download.\n\nThe HTTP status of a failed download is now recorded for any status of 300 or more. Before, it was recorded only from 400 up.\n\n**Why**\n\nThis only matters when a custom settings address is in use. A redirect there now ends the download straight away rather than being tried again.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}