{"version":"2.1.239","anchor":"missing-published-files-get-their-own-404-message","canonical_anchor":"missing-published-files-get-their-own-404-message","heading":"Missing published files get their own 404 message","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/missing-published-files-get-their-own-404-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Missing published files get their own 404 message\n\nAsking for a missing file from a published artifact now returns its own 404 message.\n\n**What**\n\nAsking for a specific file from a published artifact and getting nothing back no longer shows the generic \"no such file\" text. It reports its own message and returns a 404 to the caller.\n\n**Details**\n\n- The message covers both causes: no file is published at that path in the served version, or artifact reads through the session gateway are not enabled for the session.\n- Reported internally as an `asset_file_not_found` outcome.\n\n**Evidence**\n\n`no file is published at that path in the served version \u2014 or artifact reads through the session gateway are not enabled for this session`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}