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

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

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 2 Nov 2011 17:22:33 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <DAEA3E28-CE99-4C8C-93E2-7C83CFAC7919@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>

On 29/10/2011, at 8:55 PM, Julian Reschke wrote:

> On 2011-10-24 20:13, Julian Reschke wrote:
>> ...
> 
> Trying to summarize where we are:
> 
> 1) Yves did dome tests on servers: <http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0266.html> -> the servers being tested didn't seem to unescape
> 
> 2) Amos Jeffries reports that recent Squids actually *do* handle them as quoted-strings: <http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0470.html>
> 
> 3) I tested various browsers, and they do not unescape: <http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0087.html>
> 
> So what do we do?
> 
> Claiming that etags use quoted-strings when almost nobody does seems to be a bad thing. For instance, apparently it has caused the Squid developers to make a change that in the best case is harmless, and in the worst case will break things.


I'm +1 on your proposal <http://www.w3.org/mid/4E5FD624.2000802@gmx.de>. 

Cheers,


--
Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 2 November 2011 06:27:36 GMT

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