|Subject:||[XMLRPC::Lite] Double UTF-8 encoding causes incorrect HTTP content-length setting|
See SourceForge bugand Bugzilla/Testopia bug 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.
Message body not shown because it is not plain text.