- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 05 May 2008 17:42:36 +0200
- To: Brian Smith <brian@briansmith.org>
- CC: 'HTTP Working Group' <ietf-http-wg@w3.org>, 'Mark Nottingham' <mnot@mnot.net>
Brian Smith wrote: > ... >>> 1. There is too much flexibility in the syntax of the "rel" >>> parameter. For >>> example, the following all mean the same thing: >>> rel=edit >>> rel="edit" >>> rel="\e\d\i\t" >>> rel="http://www.iana.org/assignments/link-relations.html#edit" >>> .... >>> If you want to be able to catch all variations, then you have to >>> write a pretty nasty regular expression. >> What leads you to believe that "\d" is the same as "d" in a URI >> reference? > > "\d" and "d" mean the same thing according to the definition of > quoted-string in RFC 2616, AFAICT. We are supposed to unescape > quoted-strings before processing them, right? > ... That seems like a very academic argument to me... Why would a server ever use escapes in a Link header? (except in order to prove a point, that is... :-) BR, Julian
Received on Monday, 5 May 2008 15:43:24 UTC