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

#306: does etag value really use quoted-string

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 26 Jul 2011 15:59:06 -0400
Message-Id: <7D198F1B-0F9D-49AA-9A14-4DE50870D1D1@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
<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.

Consider a response with:

ETag: "\a"

And a subsequent request:

PUT /foo
If-Match: "a"

Proposal:

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.


--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 26 July 2011 19:59:41 GMT

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