There is a bug related to UTF8 in current version of HttpBindServlet. I’ve attached patch.
Index: openfire/src/org/jivesoftware/openfire/http/HttpBindServlet.java =================================================================== --- openfire/src/org/jivesoftware/openfire/http/HttpBindServlet.java Thu May 01 12:51:39 AZST 2008 +++ openfire/src/org/jivesoftware/openfire/http/HttpBindServlet.java Thu May 01 12:51:39 AZST 2008 @@ -99,7 +99,7 @@ } queryString = URLDecoder.decode(queryString, "utf-8"); - parseDocument(request, response, new ByteArrayInputStream(queryString.getBytes())); + parseDocument(request, response, new ByteArrayInputStream(queryString.getBytes("utf-8"))); } private void sendLegacyError(HttpServletResponse response, BoshBindingError error)
I did create JM-1351.
Setting “-Dfile.encoding=UTF-8” as a start parameter solves a few issues, maybe also this one without a code change.
It solves this issue, but that code change is needed anyway. There is two alternatives: use UTF-8 or use default charset in all servlet string-bytes conversions.
Any comment on the current status of this patch ?
(just attempting to sort thru old issues in jira and see what their status is…)