Re: POST Vs GET

Ravi, The POST should work. Here's an example that works within tomcat. curl -X POST --data "q=*:*&rows=1" http://localhost:8080/solr/collection1/select Sameer. On Mon, Jun 23, 2014 at 10:37 AM, EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions) wrote: > Hi, I am executing a solr que

RE: POST Vs GET

obust on handling all these heading.. May be i can think about running in Jetty in production. --Ravi -Original Message- From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] Sent: Monday, June 23, 2014 2:30 PM To: solr-user@lucene.apache.org Subject: Re: POST Vs GET Why don&

Re: POST Vs GET

Why don't you just use the jetty shipped with Solr? It has all the correct defaults. In future, we may not even support shipping a war file. On Mon, Jun 23, 2014 at 11:07 PM, EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions) wrote: > Hi, I am executing a solr query runs 10 to 12 lines

POST Vs GET

Hi, I am executing a solr query runs 10 to 12 lines with all the boosting and condition. I change the Http Contentype to POST from GET as post doesn't have any restriction for size. But I am getting an error. I am using Tomcat 7, Is there any place we need to specify in Tomcat to accept POST..

Re: POST VS GET and NON English Characters

You need to do something like this in the ./conf/tomcat server.xml file: See 'URIEncoding' in http://tomcat.apache.org/tomcat-7.0-doc/config/http.html Note that this will assume that the encoding of the data is in utf-8 if (and ONLY if) the charset parameter is not set in the HTTP request

Re: POST VS GET and NON English Characters

Paul , I added the fllowing line to catalina.sh and restarted the server ,but this does not seem to help. JAVA_OPTS="-Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8" Regards Sujatha On Sun, Jul 17, 2011 at 3:51 AM, Paul Libbrecht wrote: > If you have the option, try setting the

Re: POST VS GET and NON English Characters

If you have the option, try setting the default charset of the servlet-container to utf-8. Typically this is done by setting a system property on startup. My experience has been that the default used to be utf-8 but it is less and less and sometimes in a surprising way! paul Le 16 juil. 2011

Re: POST VS GET and NON English Characters

It works fine with GET method ,but I am wondering why it does not with POST method. 2011/7/15 pankaj bhatt > Hi Arun, > This looks like an Encoding issue to me. > Can you change your browser settinsg to UTF-8 and hit the search url > via GET method. > >We faced the similar

Re: POST VS GET and NON English Characters

Hi Arun, This looks like an Encoding issue to me. Can you change your browser settinsg to UTF-8 and hit the search url via GET method. We faced the similar problem with chienese,korean languages, this solved the problem. / Pankaj Bhatt. 2011/7/15 Sujatha Arun > Hello,

POST VS GET and NON English Characters

Hello, We have implemented solr search in several languages .Intially we used the "GET" method for querying ,but later moved to "POST" method to accomodate lengthy queries . When we moved form GET TO POSt method ,the german characteres could no longer be searched and I had to use the fucntion