[ https://issues.apache.org/jira/browse/SOLR-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781681#action_12781681 ]
Hoss Man commented on SOLR-1576: -------------------------------- At the moment the response formatting is at the whim of the servlet container -- so you do get additional information, but it's servlet container dependent on how that error information is formatted. SOLR-141 aims to fix that by allowing response writer specific formatting of the underlying exception so the client has all the data available. > Provide better error reporting for clients performing updates (or other > operations) > ----------------------------------------------------------------------------------- > > Key: SOLR-1576 > URL: https://issues.apache.org/jira/browse/SOLR-1576 > Project: Solr > Issue Type: Improvement > Components: update > Affects Versions: 1.4 > Reporter: Paul R. Brown > Priority: Minor > > It's frustrating from a client point of view to perform an update and then > get back a {{400}} with no additional information. Would it make sense to > supply an HTTP header with information about the error? I was thinking > something like: > {code}X-SOLR-ERROR-MESSAGE: unknown field 'fooBarBaz'{code} > This would snap right into {{SolrDispatchFilter}} in {{sendError}} at line > 363: > {code}res.addHeader("X-SOLR-ERROR-MESSAGE",ex.getMessage());{code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.