The status also can't be read when the server is not reachable. Also the readyState goes through status 2 (statusLoaded) and 3 (statusInteractive) before reaching 4.
12 years ago
I am experiencing the same phenomenon. A workaround is to catch the exception, although the exception should not have been thrown, as request.readyState should not have had a value of 4.
This bug still occurs in FireFox 1.5 Beta 1.
Still happens on FF1.7 when the server is terminated before the request is sent. A status field like this needs to handle this situation.
Created attachment 204399 [details] [diff] [review] Possible fix We can't return "undefined" for an integer, but we can do the same thing as for a non-HTTP request -- return 0.
Comment on attachment 204399 [details] [diff] [review] Possible fix r=darin Please document this in nsIXMLHttpRequest. Is this documented in the Web Apps spec? Should it be? What do other browsers do?
Comment on attachment 204399 [details] [diff] [review] Possible fix Per conversation with hixie, something like a 5xx code would make more sense here... Stephen, Gabriel, Willem, what status code does IE return in this case?
> Per conversation with hixie, something like a 5xx code would make more sense > here... Really? 5xx seems to implicate the server, but that's not accurate. Also, don't we need to worry about changing the API in an incompatible way? What should the status codes be for 'file:' URLs?
I'd be aiming to not change anything for file: urls -- those would continue to return 0. 502 doesn't necessarily implicate the server you were trying to contact... Unfortunately, all the HTTP status codes do assume the server was contacted; none of them really mean "server didn't respond". 502 is the closest.
> I'd be aiming to not change anything for file: urls -- those would continue to > return 0. OK > 502 doesn't necessarily implicate the server you were trying to contact... > Unfortunately, all the HTTP status codes do assume the server was contacted; > none of them really mean "server didn't respond". 502 is the closest. 502 means there was a bad gateway. That doesn't really sound accurate to me. The first sentence of section 10.5 says: "Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request." That really doesn't describe the case of a server response that is still pending.
For still pending we want to keep throwing. I think we should only change behavior for cases where our readyState is 3 or 4 (which means either OnDataAvailable or OnStopRequest has been called). But network timeout will call OnStopRequest, as will connection refused, etc, right?
onStopRequest will always be called if asyncOpen returned success. so, yes.
Created attachment 205440 [details] [diff] [review] Updated patch This makes sure we still throw if readyState is not 3 or 4 (so if we're still waiting on initial server response). I sort of randomly decided that the generic 500 status code is good enough here, but I really don't care that much what we make it. IE uses 12029, which is ERROR_INTERNET_CANNOT_CONNECT (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/wininet_errors.asp). I don't really think we want to be following IE to the extent of using that status code; if we do decide to go that way, we should use whatever error status our OnStopRequest got.... ;)
Comment on attachment 205440 [details] [diff] [review] Updated patch sr=jst
> I don't really think we want to be following IE to the extent of using that > status code; if we do decide to go that way, we should use whatever error > status our OnStopRequest got.... ;) Perhaps an internal error code would be more useful than a made-up 500 response that looks like it came from the server. Synthesizing a 500 response is bound to confound someone, who may end up blaming the server for the wrong thing, look in the server logs, wonder why the server logs show no 500 response, and so on...
I could just return NS_ERROR_NOT_AVAILABLE as the int, sure. Want me to?
The problem there is whether WHATWG can interoperably specify this. It seems like that would be desirable, but with NS_ERROR_NOT_AVAILABLE it's tough.
A WG could easily just say that the useragent will throw an error and not specify the error, right?
But we're not throwing an error. We're returning an integer. The error case we're going to throw NOT_AVAILABLE and be done with it; the problem is the non-error case.
I think we should consider doing what IE does.... looks like we haven't figured that out yet. Do we have a testcase? Probably not, right?... because it is difficult to simulate a network timeout?
Hixie wrote a testcase for this, actually, so we do know exactly what IE does. See comment 13 -- it returns an "HTTP status" of 12029, which corresponds to a WinAPI status code.
Sorry, I missed that while scrolling back through the comments. So, do you really think that faking a legit server response code is the best solution here? It doesn't feel right to me... perhaps we should have our own internal status code as well. Otherwise, we are overloading the meaning of the HTTP 5xx status codes.
Yeah, I have to admit that 500 does make me somewhat unhappy... ;) Our internal status code would be NS_ERROR_NOT_AVAILABLE, I guess.
Yes, let's just return that then. I think that's more reasonable.
Created attachment 209107 [details] [diff] [review] Updated to comments
Fixed. If someone feels a need for this to land on the 1.8 branch (so for Firefox 2), please request approval.
The specification http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8 currently says that you have to set all members of the object to their initial values (excluding readyState). If you want this to change, by setting status to 500 for instance you should probably raise this on public-webapi.
I don't think we really care so much what we return here. I'm happy to return 0, as the spec would require. We're going to need so many changes to implement that spec that it'll be more or less a wholesale rewrite of this file, though. I figure once the spec is in CR and there are tests (so we can test said rewrite) we'll file a bug to implement that spec.
Ah, thanks for the heads up!