Bug 50433
| Summary: | NETWORK_ERR: XMLHttpRequest Exception 101 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Douglas Rhiner <douglasrhiner> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Major | CC: | annevk, ap, douglasrhiner, ribob2 |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.6 | ||
| URL: | http://www.govtour.com/analytics/spec_results.php?pid=157118 | ||
Douglas Rhiner
When requesting the URL provided:
http://www.govtour.com/analytics/spec_results.php?pid=157118
In Safari ONLY I get the following error.
NETWORK_ERR: XMLHttpRequest Exception 101
This is very frustrating since the majority of the users who will be accessing this prefer to use Safari.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
This URL cannot be opened - it redirects to an authentication page. Is this a test installation for which you could provide username and password?
Ribo
I've observed this exception on Android 2.35/Webit 533.1 For me and others (reporting on stackOverflow.com) the problem seems to be related to cross domain use of XMLHttpRequest. (I don't see much detail to this bug report, perhaps this or these are different issues.)
What I observed is that a cross domain XMLHttpRequest would fail with this exception on the second and subsequent requests to the same url. (The first request worked (the site supports cross domain requests and the response is correct.) Subsequent requests to the same URL (synchronous or asynchronous) got this exception. For async requests, the onload event with responseState==4 occurred, with status==0 responseText="" and responseXML=null Changing the URL by adding some benign junk to the end of the URL caused it to work once then fail again. -- Almost like it was trying to reject requests for 'cached' pages.
Other people on stackOverflow.com complained about getting the exception if the XML response was incorrect or for other cross domain issues. --These may be legitimate exceptions (None of us could find documentation on what this exception is supposed to mean.
Anne van Kesteren
Per code inspection this exception appears to be no longer there. Resolving as INVALID as there's no working test case.