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

Re: CRLF requirement

From: Martin Nilsson <nilsson@opera.com>
Date: Wed, 02 Jul 2014 01:18:17 +0200
To: ietf-http-wg@w3.org
Message-ID: <op.xicdornoiw9drz@uranium.homerun.telia.com>
On Tue, 01 Jul 2014 17:54:11 +0200, Julian Reschke <julian.reschke@gmx.de>  
wrote:

> On 2014-07-01 17:35, Anne van Kesteren wrote:
>> On Tue, Jul 1, 2014 at 5:29 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>> On 01 Jul 2014, at 17:05, Anne van Kesteren <annevk@annevk.nl> wrote:
>>>> That is not what happens in the most popular clients today.
>>>
>>> I’m still curious why you think that’s relevant.
>>
>> Network effects. Content will end up relying on quirks of dominant
>> players, especially if those quirks are stable and interoperable among
>> a class of clients such as browsers.
>
> That's true when the "bug" is likely to happen, such as creating broken  
> filename parameters in Content-Disposition by just using string  
> concatenation (causing whitespace and non-ASCII to appear where they do  
> not belong).
>
> But here? Why would anybody do this, even by accident?
>

With compliments from our bug database:

"HTTP/1.1 200 \r"
"Content-Type: image/gif\r"
"nnCoection: close\r"
"Content-Length: 42\r"
"Cache-Control: no-cache\r"
"Pragma: no-cache\r"
"\n"

(followed by 42 bytes of gif)

/Martin Nilsson

-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/
Received on Tuesday, 1 July 2014 23:18:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC