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

@annevk By "treat this as a clarification issue", you mean continuing to preserve percent-encoding of characters outside the [RFC 3986 reserved set](https://www.rfc-editor.org/rfc/rfc3986#section-2.2) in https://url.spec.whatwg.org/#path-state ? That is permitted by the [current HTTP semantics document](https://www.rfc-editor.org/rfc/rfc9110#section-4.2.3) (which does not require normalization but does make clear that such gratuitous encoding maintains the interpretation of a URI, i.e. it still identifies the same resource), although it _does_ put more burden on user code that is trying to be robust. How would you feel about an issue requesting a `normalize` method?

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

Message ID: <whatwg/url/issues/606/1355211556@github.com>