Skip Menu |

This queue is for tickets about the RPC-XML CPAN distribution.

Report information
The Basics
Id: 61333
Status: rejected
Priority: 0/
Queue: RPC-XML

People
Owner: Nobody in particular
Requestors: joey [...] kitenet.net
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 0.60
  • 0.61
  • 0.62
  • 0.63
  • 0.64
  • 0.65
  • 0.66
  • 0.67
  • 0.69
  • 0.70
  • 0.71
  • 0.72
  • 0.73
Fixed in: (no value)



Subject: RPC::XML::Client crashing on unicode input
A call to XML::RPC::Client->send_request crashed when user input included a unicode elipses (…) and this had been decoded into perl's internal character representation. On 0.73, the error is: Error: Wide character in subroutine entry at /usr/share/perl5/RPC/XML.pm line 402. On 0.60, it is instead: Error: HTTP::Message content must be bytes at /usr/share/perl5/RPC/XML/Client.pm line 308 I was able to work around this by calling encode_utf8 on all user- supplied data in the RPC request, but I think it's hard to remember to do that, and it's very suprising since unicode encoding is common in XML.
You know, I remembered I had some other code that was using XML::RPC ok with unicode. The crashing code did not set RPC::XML::ENCODING. You may want to NOTABUG this. But I don't think the documentation of ENCODING makes very clear that it's required to use unicode at all. And not supporting unicode by default is arguably a bad default these days.
On Tue Sep 14 15:17:53 2010, JOEY wrote: Show quoted text
> You know, I remembered I had some other code that was using XML::RPC ok > with unicode. The crashing code did not set RPC::XML::ENCODING. > > You may want to NOTABUG this. But I don't think the documentation of > ENCODING makes very clear that it's required to use unicode at all. And > not supporting unicode by default is arguably a bad default these days.
Er, actually, I tried setting ENCODING, and it didn't help in this crash.
This is a duplicate of bug #34472: https://rt.cpan.org/Ticket/Display.html?id=34472
On Sat Jan 15 03:55:52 2011, AAR wrote: Show quoted text
> This is a duplicate of bug #34472: > https://rt.cpan.org/Ticket/Display.html?id=34472
I agree-- the base issue here is the lack of proper encoding support, which in this case happened to arise in the case of the one Unicode character in the input stream. I will mark this as a dup and connect it to the earlier bug. Randy -- """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" """"""" Randy J. Ray Silicon Valley Scale Modelers: http://www.svsm.org rjray@blackperl.com randy.j.ray@gmail.com
RT doesn't seem to have the equivalent of "this is a duplicate of XYZ". So putting 34472 in the "Refers to" field and marking this as "rejected". Please note that this is not being ignored, it should be fixed by the same (eventual) fix that takes care of 34472. Randy -- """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" """""" Randy J. Ray Silicon Valley Scale Modelers: http://www.svsm.org rjray@blackperl.com randy.j.ray@gmail.com