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

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 05 Sep 2011 15:27:02 +0200
Message-ID: <4E64CE26.4040909@gmx.de>
To: Yves Lafon <ylafon@w3.org>
CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 2011-09-05 15:17, Yves Lafon wrote:
> On Thu, 1 Sep 2011, Julian Reschke wrote:
>
>>
>> 2.3. ETag
>>
>> The ETag header field provides the current entity-tag for the
>> selected representation. An entity-tag is an opaque validator for
>> differentiating between multiple representations of the same
>> resource, regardless of whether those multiple representations are
>> due to resource state changes over time, content negotiation
>> resulting in multiple representations being valid at the same time,
>> or both. An entity-tag consists of an opaque quoted string, possibly
>> prefixed by a weakness indicator.
>>
>> ETag = entity-tag
>>
>> entity-tag = [ weak ] opaque-tag
>> weak = %x57.2F ; "W/", case-sensitive
>> opaque-tag = DQUOTE *etagc DQUOTE
>> etagc = %x21 / %x23-7E / obs-text
>> ; VCHAR except double quotes, plus obs-text
>
> How about removing %x5C as well '\' and note that implementations were
> not handling \ as a quoted-string as it was defined before, leading to
> non-interoperable parsing of such ETags.
> ...

The reason I didn't do it is that I really don't believe \ is 
non-interoperable in practice, as the clients really do not treat the 
(most?) etags as quoted strings but as opaque values; in which case 
there is no problem in practice...
Received on Monday, 5 September 2011 13:27:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:47 GMT