Re: Expected mime type application/octet-stream but got text/html

2018-09-07 Thread Shawn Heisey
On 9/6/2018 12:29 PM, nalsrini wrote: Here is the error message I am getting: https://screencast.com/t/XwEjA22jX Alexandre covered things quite well.  It looks like you're using an invalid URL. Your original message shows this code: SolrClient client = new

Re: Expected mime type application/octet-stream but got text/html

2018-09-06 Thread Alexandre Rafalovitch
Why is this http://host:port/solr-master/get? The normal URL is http://host:port/solr//. "get" as a handler is fine, can be empty for "collection1" in older Solr. But what is "solr-master" here and where is the required "/solr" part? What is your collection name? So, to me, either your URL is

Re: Expected mime type application/octet-stream but got text/html

2018-09-06 Thread Walter Underwood
I thought there was a fix for this in SolrJ. This is a bug. It is getting some error, like a 400 or 503, but instead of reporting the error, it makes a different error about the content-type. That is just busted, but I can’t find a Jira for it. wunder Walter Underwood wun...@wunderwood.org

Re: Expected mime type application/octet-stream but got text/html

2018-09-06 Thread nalsrini
Here is the error message I am getting: https://screencast.com/t/XwEjA22jX -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Expected mime type application/octet-stream but got text/html

2018-09-04 Thread Shawn Heisey
On 9/4/2018 3:22 PM, nalsrini wrote: Hi,I use Solr 5.3 and I don't have any collection. When I execute the following code, I got this error:Error from server at http://:/solr-master: Expected mime type application/octet-stream but got text/html.SolrClient client = new

Re: Expected mime type application/octet-stream but got text/html

2018-03-05 Thread Jeff Dyke
I'm not sure where you're documents are coming from but i would find this from a 403/404 in an S3 bucket if the permissions were not correct. But ultimately Walters last sentence is the best next step. On Mon, Mar 5, 2018 at 12:38 PM, Walter Underwood wrote: > I presume

Re: Expected mime type application/octet-stream but got text/html

2018-03-05 Thread Walter Underwood
I presume this error is from SolrJ. SolrJ has requested responses in javabin format, so it uses that parser. When there is an error, often a 503 (timeout), the body of the HTTP response is in HTML. When that happens, this error results. This was fixed in SolrJ sometime in the 5.x releases. To

Re: Expected mime type application/octet-stream but got text/html

2018-03-05 Thread mustafiz
Hi Dear, I am facing exactly same issue for my dspace 6.1 but can't solving after 3 days working. as i am new on dspace. can you please help me detail how i can get rid from it? details please. Thanks -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Expected mime type application/octet-stream but got text/html

2017-10-17 Thread Jason Gerlowski
At a glance, I'd guess that your SolrClient object isn't setup correctly, probably because it has the wrong "baseURL" specified. Solr has a "/solr//update" URL, but the error above makes it look like your application is reaching out to "/solr/update" which isn't a valid endpoint. If your

Re: Expected mime type application/octet-stream but got text/html

2015-12-18 Thread Andrej van der Zee
Hi, > Fixed on erick's behalf because he had to run to a meeting... > > https://cwiki.apache.org/confluence/display/solr/Distributed+Requests > > ...i also wen't ahead to shift the examples to more emphasize using shard > Ids since that's probably safer/cleaner for most people. > Thanks for the

RE: Expected mime type application/octet-stream but got text/html

2015-12-17 Thread Markus Jelsma
Hi - looks like Solr did not start up correctly, got some errors and kept Jetty running. You should find information in that node's logs. M. -Original message- > From:Andrej van der Zee > Sent: Thursday 17th December 2015 10:32 > To:

Re: Expected mime type application/octet-stream but got text/html

2015-12-17 Thread Andrej van der Zee
It turns out that the documentation is not correct. If I specify the collection name after shards=, it does work as expected. So this works: curl " http://54.93.121.54:8986/solr/connects/select?q=*%3A*=json=true=1000=54.93.121.54:8986/solr/connects " This does not work: curl "

Re: Expected mime type application/octet-stream but got text/html

2015-12-17 Thread Erick Erickson
Andrej: Indeed, it's a doc problem. A long time ago in a Solr far away, there was a bunch of effort to use the "default" collection (collection1). When that was changed, this documentation didn't get updated. We'll update it in a few, thanks for reporting! Erick On Thu, Dec 17, 2015 at 1:39

Re: Expected mime type application/octet-stream but got text/html

2015-12-17 Thread Chris Hostetter
: : Indeed, it's a doc problem. A long time ago in a Solr far away, there : was a bunch of effort to use the "default" collection (collection1). : When that was changed, this documentation didn't get updated. : : We'll update it in a few, thanks for reporting! Fixed on erick's behalf because he

Re: Expected mime type application/octet-stream but got text/html

2015-04-28 Thread Vijaya Narayana Reddy Bhoomi Reddy
Just to add, my solrconfig.xml is the standard one, with no modifications. It was taken directly from the collection1 core from 4.10.2 installation. However, in schema.xml, I have added my own fields. Hope it has got nothing to do with schema.xml Thanks Regards Vijay

RE: Expected mime type application/octet-stream but got text/html

2015-04-28 Thread Stephan Schubert
Hi, just a wild guess: you are calling /solr/update instead of /solr/collection/update Regards Stephan Von:Vijaya Narayana Reddy Bhoomi Reddy vijaya.bhoomire...@whishworks.com An: solr-user@lucene.apache.org, Datum: 28.04.2015 13:57 Betreff:Expected mime type

Re: Expected mime type application/octet-stream but got text/html

2015-04-28 Thread Vijaya Narayana Reddy Bhoomi Reddy
Thanks Stephen, that was the issue. In the URL, I missed the solr part. Thanks for your help. Functionality is working fine now. Thanks Regards Vijay On 28 April 2015 at 13:05, Stephan Schubert stephan.schub...@sick.de wrote: Hi, just a wild guess: you are calling /solr/update instead of