W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: #306: does etag value really use quoted-string

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>
Message-ID: <alpine.DEB.1.10.1107261740120.8531@wnl.j3.bet>
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.

Received on Tuesday, 26 July 2011 21:44:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:58 UTC