[jira] Commented: (SOLR-443) POST queries don't declare its charset

["Yonik Seeley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606474#action_12606474 ] 

Yonik Seeley commented on SOLR-443:
-----------------------------------

I just tested the latest 5.5 tomcat (5.5.26).
It appears that the coding of x-www-form-urlencoded assumes the  the same as that of the URI encoding now (percent encoded UTF-8 rather than latin-1 if configured that way).  I'm not sure if it was like that in the past, but it works now at least!

Just set URIEncoding="UTF-8" for the connector...
see http://wiki.apache.org/solr/SolrTomcat under "URI Charset Config"

> POST queries don't declare its charset
> --------------------------------------
>
>                 Key: SOLR-443
>                 URL: https://issues.apache.org/jira/browse/SOLR-443
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 1.2
>         Environment: Tomcat 6.0.14
>            Reporter: Andrew Schurman
>            Priority: Minor
>         Attachments: SOLR-443-multipart.patch, solr-443.patch, solr-443.patch, SolrDispatchFilter.patch
>
>
> When sending a query via POST, the content-type is not set. The content charset for the POST parameters are set, but this only appears to be used for creating the Content-Length header in the commons library. Since a query is encoded in UTF-8, the http headers should also specify content type charset.
> On Tomcat, this causes problems when the query string contains non-ascii characters (characters with accents and such) as it tries to parse the POST body in its default ISO-9886-1. There appears to be no way to set/change the default encoding for a message body on Tomcat.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.