Redstone XML-RPC Library / Bugs / #27 Incorrect content-length calculation in XmlRpcServlet

Incorrect content-length calculation in XmlRpcServlet

#27 Incorrect content-length calculation in XmlRpcServlet

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2011-07-21

Created: 2011-07-21

Creator: Anonymous

Private: No

When cacluating the content length for XMLRPC replies, the current implementation of XMLRPC servelet just serializes the response into a string and gets its length. This gives the number of characters in the string and not the number of encoded bytes. There is a difference between the two when dealing with characters with multi byte encodings (e.g. kanji characters when encoded in UTF-8), and this results in truncated responses from the XmlRpcServelet when sending responses with such characters.

Patch for fix attached

Discussion

Nobody/Anonymous - 2011-07-21

fix_for_content_length.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nadir Kiyanclar - 2011-07-22

submitted by nadir@amazon.com (sorry, forgot to log in before submitting this comment)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nadir Kiyanclar - 2011-07-22

before submitting this bug, not comment

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Incorrect content-length calculation in XmlRpcServlet

Group

Searches

Help

#27 Incorrect content-length calculation in XmlRpcServlet

Discussion