W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: Bad browser behaviour?

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 20 Mar 2012 16:40:45 +1100
Cc: "Adam Barth" <w3c@adambarth.com>, "HTTP Working Group" <ietf-http-wg@w3.org>
Message-Id: <E2095BF9-1DB6-4777-B248-1B0678F042D2@mnot.net>
To: "Adrien W. de Croy" <adrien@qbik.com>
It might be worth differentiating between the download use case and normal browsing. 

Also, in both cases, it would be good to highlight incomplete transfers in the console.

Note that all of this really isn't part of HTTP, per se, but rather how browsers choose to use it.

Cheers,


On 20/03/2012, at 4:37 PM, Adrien W. de Croy wrote:

> 
> OK, so what we're saying is that the 0 chunk is basically redundant.
> 
> ------ Original Message ------
> From: "Adam Barth" <w3c@adambarth.com>
> To: "Adrien W. de Croy" <adrien@qbik.com>
> Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
> Sent: 20/03/2012 6:34:44 p.m.
> Subject: Re: Re[2]: Bad browser behaviour?
>> I suspect these things would just annoy users with unreliable network
>> connections.  Wouldn't you be frustrated if a web page you were
>> looking at suddenly went blank just because your WiFi cut out?
>> 
>> Adam
>> 
>> 
>> On Mon, Mar 19, 2012 at 10:16 PM, Adrien W. de Croy <adrien@qbik.com> wrote:
>> 
>>> 
>>> what about pop a warning, or clear the page?
>>> 
>>> 
>>> ------ Original Message ------
>>> From: "Adam Barth" <w3c@adambarth.com>
>>> To: "Adrien W. de Croy" <adrien@qbik.com>
>>> Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
>>> Sent: 20/03/2012 6:02:34 p.m.
>>> Subject: Re: Bad browser behaviour?
>>> 
>>>> 
>>>> 
>>>> It's probably impossible for browsers to do anything else given that
>>>> browsers incrementally render chunk-transfered content.  For example,
>>>> if the network were to hang at that point (rather than drop), they'd
>>>> do the same thing.
>>>> 
>>>> Adam
>>>> 
>>>> 
>>>> On Mon, Mar 19, 2012 at 7:20 PM, Adrien W. de Croy <adrien@qbik.com>
>>>> wrote:
>>>> 
>>>> 
>>>>> 
>>>>> 
>>>>> Hi all
>>>>> 
>>>>> we're seeing some (IMO) undesirable behaviour for all tested current
>>>>> browsers (we tested FF, Chrome, IE and Opera).
>>>>> 
>>>>> It relates to abortive closes on chunked transfers.  In this case, I'm
>>>>> talking about a server close prior to the final 0 chunk.
>>>>> 
>>>>> All the browsers we tested ignore this and display the content with no
>>>>> warning whatsoever.
>>>>> 
>>>>> For our proxy to treat it as an abortive close is therefore a problem in
>>>>> our
>>>>> customers' eyes.
>>>>> 
>>>>> So what's the deal?  Should we allow this behaviour in the spec?  Or
>>>>> should
>>>>> browser vendors be encouraged to break the page / download?
>>>>> 
>>>>> Isn't it a potential security issue?
>>>>> 
>>>>> Adrien
>>>>> 
>>>>> 
>> 
> 
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 20 March 2012 05:41:13 GMT

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