lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunnar Wagenknecht (JIRA)" <>
Subject [jira] Commented: (SOLR-443) POST queries don't declare its charset
Date Mon, 23 Jun 2008 06:36:45 GMT


Gunnar Wagenknecht commented on SOLR-443:

So what about making this configurable? It looks like the server side allows both ways. It
looks to me that {{Content-Type: application/x-www-form-urlencoded; charset=UTF-8}} basically
works but there is no 100% guarantee. On the other hand, multi-part POSTs have a guarantee
but come with a performance penalty. I think it would be fair to document both option and
let the API client decide which one would better fit his use case.

> POST queries don't declare its charset
> --------------------------------------
>                 Key: SOLR-443
>                 URL:
>             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.

View raw message