For this type of "walking" error, I'd suggest installing on the "client" pc a
HTTP, HTTPS packet inspector like Fiddler; this allows you to see exactly what
information you are sending to the server, and the response that you receive;
format, image (if any) and the like.
http://fiddlerbook.com/book/
http://www.telerik.com/fiddler
Steve
> From: mark.fenb...@noaa.gov
> Subject: Re: Google didn't help on this one!
> To: solr-user@lucene.apache.org
> Date: Tue, 15 Sep 2015 13:43:47 -0400
>
> So I ran "nc -l 8983" then restarted solr, and then ran my app with my
> query. nc reported the following:
>
> GET
> /solr/EventLog/spellCheckCompRH?qt=%2FspellCheckCompRH&q=Some+more+text+wit+some+missspelled+wordz.&spellcheck=on&spellcheck.build=true&wt=javabin&version=2
>
> HTTP/1.1
> User-Agent: Solr[org.apache.solr.client.solrj.impl.HttpSolrClient] 1.0
> Host: dell9-tir:8983
> Connection: Keep-Alive
>
> I'm not sure if this is good, or indicates an error of any kind.
>
> Anyway, when I ran my app again, I got a completely different error,
> although I didn't change anything! So, I guess I get to move on from
> this and see what other hurdles I run into!
>
> Thanks for the help!
> Mark
>
>
> On 9/15/2015 11:13 AM, Yonik Seeley wrote:
> > On Tue, Sep 15, 2015 at 11:08 AM, Mark Fenbers <mark.fenb...@noaa.gov>
> > wrote:
> >> I'm working with the spellcheck component of Solr for the first time. I'm
> >> using SolrJ, and when I submit my query, I get a Solr Exception: "Expected
> >> mime type octet/stream but got text/html."
> >>
> >> What in the world is this telling me??
> > You're probably hitting an endpoint on Solr that doesn't exist and
> > getting an HTML 404 error page rather than the response (which would
> > be in binary by default).
> >
> > An easy way to see what SolrJ is sending is to kill your solr server, then
> > do
> >
> > nc -l 8983
> >
> > And then run your SolrJ program to see what it sends... if it look OK,
> > then try sending the request from curl to Solr.
> >
> > -Yonik
> >
>
