You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
evancz
changed the title
Url.Parser.s gives wrong result when path segment uses percent-encoding
s should call percentDecode before matching segment
Feb 9, 2021
While according to RFC 3986 segments should be percent-decoded before matching, making e.g. segments %6f, %6F and o equivalent, according to newer URL Living Standard decoding is not done making those three segments non-equivalent.
The URL Living Standard is a bit vague about the intended behavior so here's an issue I opened about the standard and where I got answer that decoding should not be done: whatwg/url#565
Url.Parser.s
doesn't percentDecode path segments for matching so it returnsNothing
instead of match if percent-encoding is used.The text was updated successfully, but these errors were encountered: