[
https://issues.apache.org/jira/browse/SOLR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492508
]
Ryan McKinley commented on SOLR-204:
------------------------------------
sendError lets the web app decide how to format the response body. Typically
they put HTML with the status code, with a footer saying the "Jetty" or "Resin"
This is what you get to configure with:
<error-page>
<exception-type>java.lang.Exception</exception-type>
<location>/error</location>
</error-page>
<error-page><error-code>404</error-code><location>/error</location></error-page>
etc
> Let solrconfig.xml configure the SolrDispatchFilter to handle /select
> ---------------------------------------------------------------------
>
> Key: SOLR-204
> URL: https://issues.apache.org/jira/browse/SOLR-204
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assigned To: Ryan McKinley
> Attachments: SOLR-204-HandleSelect.patch,
> SOLR-204-HandleSelect.patch, SOLR-204-HandleSelect.patch
>
>
> The major reason to make everythign use the SolrDispatchFilter is that we
> would have consistent error handling. Currently,
> SolrServlet spits back errors using:
> PrintWriter writer = response.getWriter();
> writer.write(msg);
> and the SolrDispatchFilter spits them back using:
> res.sendError( code, ex.getMessage() );
> Using "sendError" lets the servlet container format the code so it shows up
> ok in a browser. Without it, you may have to view source to see the error.
> Aditionaly, SolrDispatchFilter is more decerning about including stack trace.
> It only includes a stack trace of 500 or an unknown response code.
> Eventually, the error should probably be formatted in the requested format -
> SOLR-141.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
