Re: [whatwg/url] Should we unescape characters in path? (#606)

What about the semantics of percent encoded sequences though? Not the additional protocol- or application specific normalisations, but the analogue of [Percent-Encoding Normalization][1] in the RFC. 

[1]: https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.2.2

I don't think the URL Standard currently states that `%61` may be considered equivalent to `a`, other than in the domain (where it is obligatory). It might even make sense to mandate that, so that it is safe to assume that e.g. `http://example/%61` and `http://example/a` _refer_ to the same resource, whether browsers normalise them to the same URL or not. 

If we do make the semantics explicit then the question arises of how to correct for invalid escape sequences. So that `%6%31` does not end up being (percent-encoding-) equivalent with `%61` and then transitively with `a`. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/606#issuecomment-927103327