Paths containing escaped characters are parsed incorrectly
Brought to you by:
niallg
A path like /a/http%3A%2F%2Fexample.com/A becomes /a/http:/example.com/A
This is because AddressParser unescapes escaped characters in path before parsing it further with PathParser. The comment and code for AddressParser.path() method suggest that this is intentional, but it is not clear why would this be desirable. This certainly results in broken handling of paths containing escaped slashes and defeats the purpose of escaping.