I found the issue. With GET, the legacy code I'm calling into was written
like so:
clientResponse =
resource.contentType("application/atom+xml").accept("application/atom+xml").get();
This is a bug, and should have been:
clientResponse = resource.accept("application/atom+xml").get();
Go
Yes, my application is in Java, no I cannot switch to SolrJ because I'm
working off legacy code for which I don't have the luxury to refactor..
If my application is sending the wrong Content-Type HTTP header, which part
is it and why the same header is working for the other query paths
such as: "/
On 8/3/2015 11:34 AM, Steven White wrote:
> Hi Everyone,
>
> I cannot figure out why I'm getting HTTP Error 500 off the following code:
> Ping query caused exception: Bad contentType for search handler
> :application/atom+xml
Your application is sending an incorrect Content-Type HTTP header tha
Hi Everyone,
I cannot figure out why I'm getting HTTP Error 500 off the following code:
// Using: org.apache.wink.client
String contentType = "application/atom+xml";
URI uri = new URI("http://localhost:8983"; +
"/solr/db/admin/ping?wt=xml");
Resource resource = client.resource(uri
