Description
spin off from SOLR-3258, it would be helpful if SolrJ, when encountering Exceptions from the ResponseParser (or perhaps before ever even handing data to the ResponseParser) did some validation of the Content-Type returned by the remote server to give better error messages in cases where miss configuration has the wrong matchup between ResponseParser and mime-type (or worse: an HTML page being returned by a non-solr server)
Attachments
Issue Links
- breaks
-
SOLR-5532 SolrJ Content-Type validation is too strict for some webcontainers / proxies, breaks on equivilent content types
- Closed
- is related to
-
SOLR-3258 Ping query caused exception..Invalid version (expected 2, but 60) or the data in not in 'javabin' format
- Closed
- relates to
-
SOLR-5291 Solrj does not propagate the root cause to the user for many errors.
- Resolved