- From: Stewart Brodie <stewart.brodie@antplc.com>
- Date: Mon, 25 Jun 2007 13:25:36 +0100
- To: public-webapi@w3.org
"Anne van Kesteren" <annevk@opera.com> wrote: > Feedback from Microsoft pointed out that the SENT state is in fact the > state that indicates that all HTTP headers have been received and that > LOADING indicates that the first few bytes of the response entity body are > in. As a result, I renamed SENT to HEADERS_RECEIVED in the editor's draft > and slightly changed the send() algorithm: > > http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8 > http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html.diff?r1=1.123&r2=1.124&f=h > > Kind regards, So now you get *three* events dispatched immediately one after the other when doing a HEAD request. Still, since the spec is just documenting IE's behaviour, you don't have a choice, I suppose. Are you going to change all the methods like getRequestHeader so that they are now valid in state HEADERS_RECEIVED - it would be just bizarre to issue an event saying that we've got the complete HTTP header and then prohibit the reading of the HTTP status and headers until the entity body has started arriving. -- Stewart Brodie Software Engineer ANT Software Limited
Received on Monday, 25 June 2007 12:27:55 UTC