async fn file(__arg0: Path<String>, headers: HeaderMap) -> ResponseExpand description
One of the three assets, or nothing.
There is no SPA fallback here and there must not be one: every view in the
app lives under the hash (/#/logs), so a path this table does not know is
not a UI route that needs rescuing — it is a request for something that does
not exist. Answering it with 200 and index.html made /health, /metrics
and every probe path an operator might try report success in HTML, which is
the one answer worse than a 404.