Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.246,
In DevelopmentSection of the release
What
Both 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.
Evidence
[artifact] asset fetch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
