- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 20 Jun 2011 07:26:33 +0200
- To: Adam Barth <ietf@adambarth.com>
- CC: Chris Weber <chris@lookout.net>, "PUBLIC-IRI@W3.ORG" <PUBLIC-IRI@w3.org>
On 2011-06-20 02:10, Adam Barth wrote: > ... >> In a similar test case "http://example.com/foo\bar" both FF and Opera's path >> property in the DOM percent-encode the "\" as "/foo%5Cbar" and the >> corresponding HTTP request matches to become "GET /foo%5Cbar HTTP/1.1". IE, >> Chrome, and Safari all instead convert the "\" to a "/". Their DOM path >> property shows "/foo/bar" and the HTTP request matches as "GET /foo/bar >> HTTP/1.1". > > Indeed. The point is that IE, Chrome, and Safari treat \ as if it > were / in parsing URLs whereas Firefox does not. I suspect we'll want ...and Opera... > the spec to say that \ should be treated like / when parsing URLs. We have two independent implementations that do it right, one of which with a large market share. I don't see why "we" would want to declare them non-compliant. Best regards, Julian
Received on Monday, 20 June 2011 05:27:03 UTC