{"version":"2.1.224","anchor":"allowlist-blocks-recognised-from-a-second-proxy-header","canonical_anchor":"allowlist-blocks-recognised-from-a-second-proxy-header","heading":"Allowlist blocks recognised from a second proxy header","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/allowlist-blocks-recognised-from-a-second-proxy-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Allowlist blocks recognised from a second proxy header\n\nArtifact fetches recognise a second proxy header as a network allowlist block.\n\n**What**\n\nArtifact fetches now treat a 403 carrying `x-deny-reason: host_not_allowed` as a network allowlist block, alongside the existing `x-proxy-error: blocked-by-allowlist`, and other failures append the proxy's deny reason to the error text. The message makes clear the artifact itself is still accessible.\n\n**Evidence**\n\n`not reachable through this environment's network allowlist; your access to the artifact itself is fine (the boot check passed)`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}