Closed Bug 143039 Opened 22 years ago Closed 22 years ago

Typo in nsXmlRpcClient.js line 94

Categories

(Core :: XML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: adamf, Assigned: samuel)

References

()

Details

Attachments

(1 file)

684 bytes, patch
hjtoi-bugzilla
: review+
hjtoi-bugzilla
: superreview+
Details | Diff | Splinter Review
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
Attached patch patchSplinter Review
Reassigning to owner of XML-RPC.
Assignee: heikki → samuel
Marking NEW as it has a patch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: patch
Why are you even hitting that line?

r=samuel@sieb.net
heikki, can you sr?
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.
checked in
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
QA Contact: petersen → rakeshmishra
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: