Thanks for the extended research. That's really helpful!
Could you please clarify what kind of errors FF is throwing ?
Also, could you please kindly advise if Safari 2's behaviour is
consistent with Safari 3 ?
On Nov 14, 12:27 am, Ken Snyder <[EMAIL PROTECTED]> wrote:
> Tobie Langel wrote:
> > Some browsers - I can't remember witch - always return a status of 0
> > for the file: protocol, others don't return a value at all in that
> > case, hence this hack.
> > We're going to be doing more work on Ajax for 1.6.1, but I'm not even
> > sure there is a real solution ot his issue.
> > Regards,
> > Tobie
> I think the trick here is to return a separate status code for files
> instead of zero. I believe it is possible to handle all situations.
> Here is the result of my research on status codes:
> Calling HTTP(S) ajax url
> Network error scenarios:
> FF2 - throws exception
> S3 - transport.status == 0
> O9 - transport.status == 0
> IE6/7 - transport.status == (one of the following)
> 1223 : Client canceled request
> 12002: Server timeout
> 12029: Dropped connection
> 12030: Dropped connection
> 12031: Dropped connection
> 12152: Connection closed by server
> Calling file-based ajax url
> Success: ALL BROWSERS - transport.status == 0
> Failure: ALL BROWSERS - transport.status == 0
> Note: for network errors on FF 1.x transport.status == 200 and no
> exception is thrown so the developer is left to see that the response is
> empty to know of a failure. I don't think there is a workaround.
> So how can we know the difference between a network error and a
> file-based url call?--Both url and location.protocol give clues.
> IMHO it is important that we properly route all these codes: file-based
> requests should always fire "onSuccess" (unless we can figure out how to
> detect a file-based failure) and any of the network error codes should
> throw "onException". Right now, we get all sorts of kooky callbacks
> such as "on0" and "on12029".
> For more info and links to my sources, see the discussion from
> - Ken Snyder
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at