On 2/12/2013 1:42 AM, o.mares wrote:
yesterday we updated from solr 4.0 to solr 4.1 and since then from time to
time following error pops up:

{msg=URLDecoder: Invalid character encoding detected after position 160 of
query string / form data (while parsing as UTF-8),code=400}:
{msg=URLDecoder: Invalid character encoding detected after position 160 of
query string / form data (while parsing as UTF-8),code=400}

Is this an issue with incorrect input data, or is something "broken" with
our solr?
Solr 4.0 did not gave us these errors.

Is your client code using UTF-8? It sounds like maybe it's not.

Thanks,
Shawn

Reply via email to