W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: update: http progress notification

From: Adrien de Croy <adrien@qbik.com>
Date: Fri, 28 May 2010 00:18:52 +1200
Message-ID: <4BFE632C.3060509@qbik.com>
To: Henrik Nordström <henrik@henriknordstrom.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>


On 27/05/2010 6:00 a.m., Henrik Nordström wrote:
> mån 2010-05-24 klockan 13:13 +1200 skrev Adrien de Croy:
>
>    
>> Tests with unmodified Firefox and IE showed no problem with multiple 102
>> responses prior to the final response as well (even though this won't be
>> an issue since the draft proposes the client explicitly advertises support).
>>      
> Hmm.. is that explicit negotiation really needed?
>    
the hop-by-hop negotiation was the justification for

a) dropping a requirement to suppress these 1xx responses for HTTP/1.0 
clients
b) not worrying about semantics of entity headers transported back in a 
1xx response.

If we drop the requirement to advertise support from the client, we 
would need to re-think these.

An alternative could be a Progress header in the request, which then 
would normally be forwarded by proxies.  Then this progress mechanism 
could work through an HTTP/1.1 proxy that didn't know about it as long 
as it forwards 1xx responses.

Regards
Adrien

> Checking.. right the specs says "Unexpected 1xx status responses MAY be
> ignored by a user agent", not MUST, so sending progress updates MAY
> break HTTP/1.1 compliant clients.
>
> The question however is if that perhaps should be a MUST?
>
> Regards
> Henrik
>
>
>    
Received on Thursday, 27 May 2010 12:19:36 GMT

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