org.apache.solr.common.SolrException: Bad contentType for search handler :text/xml; charset=UTF-8 request={q={!lucene}*:*=flat=true=json=all=false}

2016-11-26 Thread varun03sh
":["error-class","org.apache.solr.common.SolrException","root-error-class","org.apache.solr.common.SolrException"],"msg":"Ping query caused exception: Bad contentType for search handler :text/xml; charset=UTF-8 request={q={!lucene}*:*=flat=true=json=all=false}"

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-23 Thread Pavel Hladik
Hi, our developers solved the problem. We are using Solarium and we had to learn Solarium to use selects with content-type: application/x-www-form-urlencoded Pavel -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text-xml-charset-UTF-8

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-23 Thread didier deshommes
On Wed, Apr 22, 2015 at 4:17 PM, Yonik Seeley ysee...@gmail.com wrote: On Wed, Apr 22, 2015 at 11:00 AM, didier deshommes dfdes...@gmail.com wrote: curl http://localhost:8983/solr/gettingstarted/select?wt=jsonindent=trueq=foundation -H Content-type:application/json You're telling

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-22 Thread Walter Underwood
hardcodes a default header Content-Type: text/xml; charset=utf-8 if none provided. Removing it solves the problem. It seems that Solr 5.1 doesn't support this content-type. -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text-xml

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-22 Thread didier deshommes
a default header Content-Type: text/xml; charset=utf-8 if none provided. Removing it solves the problem. It seems that Solr 5.1 doesn't support this content-type. -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text-xml-charset

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-22 Thread Yonik Seeley
On Wed, Apr 22, 2015 at 11:00 AM, didier deshommes dfdes...@gmail.com wrote: curl http://localhost:8983/solr/gettingstarted/select?wt=jsonindent=trueq=foundation; -H Content-type:application/json You're telling Solr the body encoding is JSON, but then you don't send any body. We could catch

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-22 Thread bengates
-handler-text-xml-charset-UTF-8-tp4200314p4201579.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-22 Thread bengates
the Url Solarium generates in my browser, I don't get the error. Maybe Solr 5.1 requires a new header which is automatically sent by the browser but not by cUrl. I'll investigate on this... Ben -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text

Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-17 Thread Pavel Hladik
-for-search-handler-text-xml-charset-UTF-8-tp4200314.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-17 Thread Chris Hostetter
to Solr -- what was the purpose of that POSTed XML data? : Date: Thu, 16 Apr 2015 22:57:30 -0700 (MST) : From: Pavel Hladik pavel.hla...@profimedia.cz : Reply-To: solr-user@lucene.apache.org : To: solr-user@lucene.apache.org : Subject: Bad contentType for search handler :text/xml; charset=UTF-8

Re: Bad contentType for search handler :text/xml; charset=UTF-8

2015-04-17 Thread Erick Erickson
: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text-xml-charset-UTF-8-tp4200314.html Sent from the Solr - User mailing list archive at Nabble.com.