{"version":"2.1.238","anchor":"artifact-fetches-blocked-by-an-egress-proxy-now-say-so","canonical_anchor":"artifact-fetches-blocked-by-an-egress-proxy-now-say-so","heading":"Artifact fetches blocked by an egress proxy now say so","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/artifact-fetches-blocked-by-an-egress-proxy-now-say-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Artifact fetches blocked by an egress proxy now say so\n\nArtifact fetches blocked by your company proxy now say the proxy refused, not just \"network error\".\n\n**What**\n\nFetching artifact JSON, comments or assets now separates a plain network failure from a proxy refusing the CONNECT, reporting `json_proxy_refused` with the connect status and a message naming the proxy.\n\n**Details**\n\n- Allowlist blocks are routed through a single shared handler.\n- Only fires when you are behind an egress proxy.\n\n**Evidence**\n\n`json_proxy_refused`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}