- From: James M Snell <notifications@github.com>
- Date: Mon, 16 Jan 2017 23:04:16 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 17 January 2017 07:04:52 UTC
I was kind of hoping it didn't but I just checked and the results are fairly surprising...
Edge does nothing with `%7C`. It ignores it the same as Firefox, Chrome and Node.js
It *does*, however, decode `%3A`, with different results based on how it appears:
```
file:///c%3a/a/b/c
```
{
href: "file:///c:/a/b/c",
pathname: "/c:/a/b/c",
protocol: "file:",
}
```
Note the decoded `:` in the `pathname`
However,
```
file://c%3a/a/b/c
```
Results in an error being thrown with the message "A security problem occurred"
The security error implies that the `%3a` is being decoded by Edge because the equivalent `file://c%7c/a/b/c` has zero problems.
--
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/210#issuecomment-273037712
Received on Tuesday, 17 January 2017 07:04:52 UTC