ISSUE-39 - Public View

Errors in XHR requests

State:

OPEN

Product:

XMLHttpRequest2

Raised by:

Dean Jackson

Opened on:

2006-03-13

Description:

We have yet to resolve what to do with errors in XHR requests, such as lack of
network, loops in redirects, etc.

There currently isn't interoperable behaviour. Using bogus statusCodes is
unnacceptable, as is throwing an exception that can only be caught on the global
object. A new value for readyState will break all content that is written
expecting there will never be a new value. One suggestion is to return a new
value for status (eg. -1) and set statusText to an error message.


References:

http://lists.w3.org/Archives/Public/public-webapi/2006Mar/att-0092/22-webapi-minutes.html

http://www.quirksmode.org/blog/archives/2005/09/xmlhttp_notes_r_2.html

Note: Some of these links may be accessible only to W3C Members.

Related emails:

1. ISSUE-39: Errors in XHR requests (from dean+cgi@w3.org on 2006-03-13)
2. Re: ISSUE-39: Errors in XHR requests (from annevk@opera.com on 2006-03-16)
3. Re: ISSUE-39: Errors in XHR requests (from ian.davis@talis.com on 2006-03-16)
4. Re: ISSUE-39: Errors in XHR requests (from mjs@apple.com on 2006-03-16)
5. ISSUE-39: XMLHttpRequest errors (from annevk@opera.com on 2006-08-11)

Related notes:

No additional notes.