It was/is a client issue. The googlebot executed a request where the search
term was CP1252 encoded, maybe the brokenn url got indexed from a third
party site.
We solved the issue by filtering all non valid utf8 chars from the search
input string because there is no proper way to check what encodi
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: I
