-
Bug
-
Resolution: Fixed
-
Medium
-
2.3, 2.4, 2.5, 2.6.0
The Apache XML-RPC server included with Confluence uses the MinML sax parser by default to parse incoming RPC requests. This parser uses the platform default character encoding to decode the incoming XML instead of standard XML procedures for determining document encoding. This can cause string corruption when the platform encoding is not compatible with the encoding and characters used in the XML-RPC call.
Apache XML-RPC server allows any JAXP standard parser to be used to parse incoming requests; we should configure it to use Xerces which is already included with Confluence and obeys the rules regarding XML document encoding.
- is related to
-
CONFSERVER-10140 XML-RPC does not handle Japanese characters in page title and content
- Closed
- relates to
-
CONFSERVER-4051 Apache XML-RPC has issues encoding and decoding UTF-8 characters sent via the XML-RPC interface
- Closed
-
CONFSERVER-4972 Glue corrupts UTF-8 in XML-RPC
- Closed