Tomcat is notorious for not having the defaults right for UTF-8. Em, I suggest you go over the suggestions in: http://wiki.apache.org/tomcat/FAQ/CharacterEncoding Also, maybe you can use wget/curl to issue your http requests from a shell which is better suited for the encoding. -- Yuval
-----Original Message----- From: Dennis Gearon [mailto:gear...@sbcglobal.net] Sent: Sunday, November 07, 2010 10:55 PM To: solr-user@lucene.apache.org Subject: Re: Tomcat special character problem In a post document, or a get document with URL encoded variables in the BODY of the document, it's possible to specify/use different encodings that are actually specified in the headers. For SURE in post, and I'm pretty sure in GET also. Dennis Gearon Signature Warning ---------------- It is always a good idea to learn from your own mistakes. It is usually a better idea to learn from others’ mistakes, so you do not have to make them yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036' EARTH has a Right To Life, otherwise we all die. ----- Original Message ---- From: Michael Sokolov <soko...@ifactory.com> To: solr-user@lucene.apache.org Cc: Em <mailformailingli...@yahoo.de> Sent: Sun, November 7, 2010 12:40:45 PM Subject: Re: Tomcat special character problem Is it possible that your original search is being posted (HTTP POST), and the character encoding of the page with the form is not UTF-8? In that case, I believe a header gets sent with the request specifying a different character set (different from parameters in the URL, for which it's not possible to specify an encoding explicitly). -Mike On 11/7/2010 10:26 AM, Em wrote: > This helped a lot, since it solved the "göteburg"-problem. > Thank you, Ken! Great help :-). > > Unfortunately there are some other encoding problems > > "fq=testcat%3Aacôme" worked, however the full url-encoded version > "fq=testcat%3Aac%F4me" does not. > > The first version is the result of submitting the form.jsp, the second is > the version when you click into the adress-bar and press enter. > > This is a real problem for me, since applications that send a query send an > urlencoded query like the second one. > > Any suggestions?
