"Anne van Kesteren" <[EMAIL PROTECTED]> wrote: > On Mon, 25 Jun 2007 14:25:36 +0200, Stewart Brodie > <[EMAIL PROTECTED]> wrote: > > 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. > > With XMLHttpRequest 2 you can just listen to the load event. I agree that
> the situation with readystatechange is far from optimal. > > > > 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. > > All methods? I changed getResponseHeader and getAllResponseHeaders. The > specification does not define getRequestHeader. I'm sorry - my brain wasn't in gear properly yesterday. I didn't mean getRequestHeader. I meant getResponseHeader(), getAllResponseHeaders(), status and statusText. -- Stewart Brodie Software Engineer ANT Software Limited
