What
Asking 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.
Details
- 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.
- Reported internally as an
asset_file_not_foundoutcome.
Evidence
no file is published at that path in the served version — or artifact reads through the session gateway are not enabled for this session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.