Closed
Bug 763557
Opened 14 years ago
Closed 14 years ago
nsIStreamListener::onStartRequest sometimes triggered with an undefined status
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: WSourdeau, Unassigned)
Details
I am using an async HTTP connection for posting data to a CGI. With CGI responsing correctly with a status of 200, it happens that the onStartRequest method of my listener is invoked with a "aRequest" parameter of which the "status" element is undefined.
My current solution is to currently to use this at the beginning of my method:
while (typeof(aRequest.responseStatus) == "undefined");
and it works. But it is a poor hack for a problem that I would think is a thread synchronization issue in the network code...
Updated•14 years ago
|
Component: General → Networking: HTTP
Product: Thunderbird → Core
QA Contact: general → networking.http
Version: 10 → 10 Branch
| Reporter | ||
Comment 1•14 years ago
|
||
Sorry, this was due to the fact that sometimes the "aRequest" object is passed via its nsIHttpChannel interface and sometimes not.
Ahhh, XPCOM!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•