lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (JIRA)" <>
Subject [jira] Assigned: (SOLR-204) Let solrconfig.xml configure the SolrDispatchFilter to handle /select
Date Thu, 26 Apr 2007 23:02:15 GMT


Ryan McKinley reassigned SOLR-204:

    Assignee: Ryan McKinley

> Let solrconfig.xml configure the SolrDispatchFilter to handle /select
> ---------------------------------------------------------------------
>                 Key: SOLR-204
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ryan McKinley
>         Assigned To: Ryan McKinley
>         Attachments: 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.

View raw message