{"version":"2.1.295","anchor":"403-refusals-now-carry-the-refused-resource","canonical_anchor":"403-refusals-now-carry-the-refused-resource","heading":"Refused (403) requests now say which resource was refused","tier":"notice","area":"Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/403-refusals-now-carry-the-refused-resource","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Refused (403) requests now say which resource was refused\n\nWhen a request is refused with HTTP 403, Claude Code now keeps the name of the refused resource from the response\n\n**What**\n\nWhen a server refuses a request with HTTP status 403, meaning access is forbidden, Claude Code now reads which resource was refused from the response and keeps it with the error. Previously only 400 errors carried extra detail, and they still do.\n\n**Why**\n\nIt is easier to see what was refused when a request is blocked.\n\n- Area: Errors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}