Line 94 reads: throw Components.Exceptions('Only HTTP is supported'); It should read: throw Components.Exception('Only HTTP is supported'); The extra "s" on Exception causes an error when init'ing the XML-RPC client. It looks liks the solution is to remove the "s" - i've searching through the rest of the file and no other calls to Components.Exceptions exist, but plenty of Components.Exception calls exist. I am also using the modified version for my company's app and it works fine.
Summary: Typo in nsXmlRpcClient.js line 95 → Typo in nsXmlRpcClient.js line 94
Reassigning to owner of XML-RPC.
Assignee: heikki → samuel
Marking NEW as it has a patch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Why are you even hitting that line? firstname.lastname@example.org heikki, can you sr?
Comment on attachment 82811 [details] [diff] [review] patch sr=heikki
Why do we hit it, and what does it hurt?
We hit it when someone (say, an enduser, or someone writing an application using XML-RPC) tries to use XML-RPC with a protocol other than http, say https. Just because the typo is in an error handler doesn't mean it shouldn't be fixed. Someone, sooner or later, will hit this error case.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.