lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <>
Subject [jira] [Commented] (SOLR-1959) SolrJ GET operation does not send correct encoding
Date Fri, 02 Sep 2011 14:52:10 GMT


Gus Heck commented on SOLR-1959:

Slightly more helpful than the RFC is a link to the tomcat configuration:

> SolrJ GET operation does not send correct encoding
> --------------------------------------------------
>                 Key: SOLR-1959
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 1.4.1, 3.2
>            Reporter: Lance Norskog
>         Attachments: SOLR-1959.patch
> The SolrJ query operation fails to set the character encoding when doing a GET. It works
when doing a POST.
> The problem is that URLs are urlencoded with UTF-8 but the Content-type: header is not
set. I tested it with "Content-Type:text/plain;charset=utf-8" and that worked. The Content-type
header encoding defaults to ISO 8859-1.
> The result is that SolrJ queries fail for any search with a character above 127. The
work around is to use a POST query instead of a GET. I have not searched for other places.
So, change: 
> {code}
> QueryResponse qr = CommonsHttpSolrServer.query(query);
> {code}
> to:
> {code}
> QueryResponse qr = CommonsHttpSolrServer.query(query, SolrRequest.METHOD.POST);
> {code}
> One quirk of this behavior is that url-bashing a query string with an ISO 8859-1 character
(like an umlaut) works in a browser, but fails in a SolrJ request.. It also searches correctly
from the admin/index.jsp and admin/form.jsp pages, because they set the content-type in the
FORM declaration. 

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message