- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Wed, 26 May 2010 14:09:02 -0700
- To: Henrik Nordström <henrik@henriknordstrom.net>
- Cc: Adrien de Croy <adrien@qbik.com>, HTTP Working Group <ietf-http-wg@w3.org>
On May 26, 2010, at 11:00 AM, 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? > > 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? No. There is nothing wrong with the recipient doing other things, like maintaining a sidebar with logs or displaying the status briefly in some status area. The fact that it isn't ignored does not imply that the recipient keels over or explodes. ....Roy
Received on Wednesday, 26 May 2010 21:09:30 UTC