`index.html` should be read from the current path first and default to `/index.html` about certified-assets HOT 1 CLOSED

The resolution is normal for URL resolution of web servers.

…of web servers that are backed by a file system, and thus can’t both have files called /some/path/to/file and /some/path/to/file/more/stuff. I don't think a web service backed by, say, a database would do that (unless it tries to emulate a filesystem backed store). So just recording that I’d expect such mangling to be done when uploading, so that the canister really just has a map from URLs to resources.

But yeah, this dissent breaks down due to the “but single page applications need that these days”, which I find still very odd and wrong… but if that’s the case I’ll play grandpa shouting at clouds.

As for the certification: I see these options.

• Insert the hash of /some/path/to/file/index.html also at /some/path/to/file/ and /some/path/to/file.
• Expose enough of the /http_assets tree to that the certifying party can re-do these resolution steps.

The former doesn’t work for the single-page-application-catch-all. The latter seems like a horrible abstraction violation to me (mapping URLs to file names should really be internal to the service, and not something that the client ought to see.)

from certified-assets.