I read this issue on the SW GitHub too. Although I agree with you that the URL schema is a reminiscence of UNIX paths and, indeed, the standard defines a [hierarchical relationship](https://url.spec.whatwg.org/#concept-url-path) of [URL path segments](https://url.spec.whatwg.org/#url-path-segment-string), the standard does not equate `/maps` with `/maps/`. Those are effectively two different URLs and the decision of both redirecting to the same content is done at application-level and so, I think it should be solved at application-level. For the maps example, it is just a matter of renaming the url to `/searchingmaps` and that's all. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/554#issuecomment-369213810
Received on Wednesday, 28 February 2018 11:41:38 UTC