{"version":"2.1.242","anchor":"egress-proxy-refusals-on-artifact-fetches-are-named-as-such","canonical_anchor":"egress-proxy-refusals-on-artifact-fetches-are-named-as-such","heading":"Egress-proxy refusals on artifact fetches are named as such","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/egress-proxy-refusals-on-artifact-fetches-are-named-as-such","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Egress-proxy refusals on artifact fetches are named as such\n\nAn artifact fetch blocked by your corporate proxy now says so instead of looking like a service failure.\n\n**What**\n\nAn artifact content fetch blocked by a corporate egress proxy now reports its own reason code and an error naming the proxy's CONNECT status, rather than a generic relay failure, so a network policy problem is distinguishable from a service problem.\n\n**Details**\n\n- A separate message explains that asset reads work only locally or from a cloud session with the gateway relay enabled.\n\n**Evidence**\n\n`artifact content fetch refused by the environment's egress proxy`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}