Closed
Bug 47129
Opened 26 years ago
Closed 26 years ago
XML-RPC client doesn't get contentLength and therefore doesn't parse responce
Categories
(Core :: XML, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: janv, Assigned: nisheeth_mozilla)
Details
when I debuged code in
mozilla/extensions/xml-rpc/src/nsXmlRpcClient.js
it was running until line 367
and then stoped at accessing channel.contentLength
and when I temporary changed channel.contentLength to count
it worked perfectly
I noticed that nsHTTPResponse::GetContentLength returned
NS_ERROR_NOT_AVAILABLE because mContentLength=-1
Maybe problems with net library?
| Reporter | ||
Comment 1•26 years ago
|
||
adding MJ to CC list
Comment 2•26 years ago
|
||
Hmmm... according to the XML-RPC spec a Content-Length MUST be present on
XML-RPC responses. Are you sure the server is sending the CL? I am not sure if
my code handles this gracefully tho.
| Reporter | ||
Comment 3•26 years ago
|
||
OK, server is not sending CL because response is generated dynamically with PHP
This have to be bug in PHP implementation of XML-RPC
I'm gonna mark this bug invalid.
Thanks
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Updated•23 years ago
|
QA Contact: petersen → rakeshmishra
You need to log in
before you can comment on or make changes to this bug.
Description
•