Skip Menu |

This queue is for tickets about the SOAP-Lite CPAN distribution.

Report information
The Basics
Id: 44755
Status: resolved
Priority: 0/
Queue: SOAP-Lite
People
Owner: Nobody in particular
Requestors: nuabaranda [...] web.de
Cc:
AdminCc:
Bug Information
Severity: Critical
Broken in: 0.710.08
Fixed in: (no value)
Attachments
truncated_xml.pcap

History Show all quoted text
  Thu Apr 02 11:40:28 2009 nuabaranda [...] web.de - Ticket created
Subject: [XMLRPC::Lite] Double UTF-8 encoding causes incorrect HTTP content-length setting
See SourceForge bug http://sourceforge.net/tracker/?func=detail&aid=2723971&group_id=66000&atid=513017 and Bugzilla/Testopia bug https://bugzilla.mozilla.org/show_bug.cgi?id=486306 for details. When getting UTF-8 encoded data with multi-byte characters from a XMLRPC::Lite-based server the multi-byte characters get double-encoded after the HTTP content-length is already calculated. This leads to truncated HTTP responses and thus invalid XML. For an example see the attached dump file.
Subject: truncated_xml.pcap
Download truncated_xml.pcap
application/octet-stream 1.7k

Message body not shown because it is not plain text.

  Mon Apr 06 07:38:29 2009 nuabaranda [...] web.de - Correspondence added
From: nuabaranda [...] web.de
More testing reveals: If the response contains at least one 3-byte UTF character the response is correctly encoded, valid and not truncated. If it only contains ASCII and 2-byte UTF characters it is handled as ASCII, thus double-encoded and finally the HTTP response is truncated resulting in invalid XML.
  Thu May 07 13:21:06 2009 nuabaranda [...] web.de - Correspondence added
Could finally fix it. Cause was a Bugzilla Webservice bug fix trying to circumvent a SOAP::Lite bug which seems to be fixed in the meantime. See mentioned Bugzilla bug report for details.
  Thu May 07 13:21:07 2009 nuabaranda [...] web.de - Status changed from 'new' to 'resolved'