- From: Yves Lafon <ylafon@w3.org>
- Date: Tue, 26 Jul 2011 17:44:31 -0400 (EDT)
- To: Mark Nottingham <mnot@mnot.net>
- cc: HTTP Working Group <ietf-http-wg@w3.org>
On Tue, 26 Jul 2011, Mark Nottingham wrote:
> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/306>
>
> As discussed in the meeting today, ETags are specified as quoted-string,
> but many implementations do not treat them as such; e.g., they don't
> handle \-escaping.
>
> Whereas in other places this is a presentation issue, with ETags, this
> is a more serious interop issue.
The issue is also:
Are implementations properly implement quoted string in general (and not
only badly in ETags)?
> Re-specify ETags as a new ABNF construct separate to quoted-string,
> where \ is not an escape character. By their nature, they cannot contain
> a double-quote character.
In that case, for implementation already "doing it right", they will fail
on \" and \\, so forbidding '\' from the ETag production seems safer.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Tuesday, 26 July 2011 21:44:36 UTC