- From: Shawn Thompson <notifications@github.com>
- Date: Wed, 19 Apr 2017 10:07:16 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 19 April 2017 17:07:56 UTC
Hey, sorry about the state issue. I've corrected the issue to what state the problem, or maybe misunderstanding, lies. The current algorithm expects a url such as: `a://b:c#d@e` To be finished with `b` as the username, no password (I assume), and `c` as the domain. I don't believe this to be a correct use-case. In order for the original example to pass the parser, you would have to just percent encode the password yourself to: `scheme://root:pass%23word@example.com` in order for the parser implementation to not resolve the `#` as a switch to the hostname state. -- 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/294#issuecomment-295348008
Received on Wednesday, 19 April 2017 17:07:56 UTC