Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Validating and escaping mismatch in pathname #112
https://url.spec.whatwg.org/#path-state says path segments is handled as following. It means characters other than URL code points are invalid.
But it also says it should escape characters other than default encode set.
This means "[", "]", "^", and "|" are invalid for URL but aren't escaped.
Chrome 49.0.2623.87 and Safari 9.1 (11601.5.17.1) doesn't escape "[" and "]" but escape "^" and "|".
As the those result, I think "[" and "]" should be added to the URL code points, but I wander "^" and "|".
Okay, so there's an intentional difference between what is conforming and what a user agent is supposed to do. At the moment "what is conforming" matches the IETF RFCs this specification replaces and "what a user agent is supposed to do" roughly matches what implementations are doing (hopefully they will all align over time).
Maybe the time has arrived we can start considering expanding "what is conforming".