{"version":"2.1.246","anchor":"artifact-fetch-responses-are-screened-before-the-auth-error-","canonical_anchor":"artifact-fetch-responses-are-screened-before-the-auth-error-","heading":"Artifact fetch responses are screened before the auth-error branch","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-fetch-responses-are-screened-before-the-auth-error-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact fetch responses are screened before the auth-error branch\n\nArtifact downloads now pass through a screening step that can stop them with a canned message.\n\n**What**\n\nBoth artifact fetch paths now run the raw status, headers and body through a shared screening step that can stop the fetch early with a canned message. It runs only for direct fetches and is skipped when the request goes through the cloud relay. The screening code and its map from reason to message live in a shared chunk, so which responses it rejects is not visible from the fetch paths themselves.\n\n**Evidence**\n\n`[artifact] asset fetch`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}