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: Wed, 27 Jul 2011 09:22:23 -0400 (EDT)
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <alpine.DEB.1.10.1107270911550.10441@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.

Here are some tests done using INM:

When resource received has ETag: "foo"

Apache 2.2:
INM: "foo"        => 304 OK
INM: "fo\o"       => 200
INM: "foo\"       => 200 OK
INM: "fo\o","foo" => 304 OK
INM: "foo\","foo" => 200 OK

MS IIS 7.5:
INM: "foo"        => 304 OK
INM: "fo\o"       => 200
INM: "foo\"       => 200 OK
INM: "fo\o","foo" => 304 OK
INM: "foo\","foo" => 304 (meaning they are not escaping " in the quoted
                            string)
Jigsaw:
INM: "foo"        => 304 OK
INM: "fo\o"       => 304 OK
INM: "foo\"       => 200 OK
INM: "fo\o","foo" => 304 OK
INM: "foo\","foo" => 200 OK


-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Wednesday, 27 July 2011 13:22:29 GMT

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