{"version":"2.1.312","anchor":"http-3xx-now-counts-as-a-retryable-failure-in-an-error-class","canonical_anchor":"http-3xx-now-counts-as-a-retryable-failure-in-an-error-class","heading":"Redirect responses now count as failures that can be retried","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/http-3xx-now-counts-as-a-retryable-failure-in-an-error-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Redirect responses now count as failures that can be retried\n\nOne check that sorts web errors now treats redirect responses, status 300 to 399, as failures, as well as server errors\n\n**What**\n\nEvery web response has a status number. Numbers from 300 to 399 mean redirects, from 400 to 499 mean problems with the request, and 500 and above mean server errors. One check that decides whether an error counts as a failure to retry now includes 300 to 399. It still includes 500 and above and most 400s.\n\n**Why**\n\nA redirect response is now treated as a failure by this check instead of being let through.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}