I agree, the display is a bit weird. But, if you check the response
headers it the response code is 400 "Bad Request"
In firefox or IE, you would need to inspect the headers to see what is going on.
The issue is that /select uses a servlet that writes out a stack trace
for every error it hits directly. Is uses:
try{response.setStatus(rc);} catch (Exception e) {}
PrintWriter writer = response.getWriter();
writer.write(msg);
Down the line, when we have
http://issues.apache.org/jira/browse/SOLR-141, this will be the best
option.
I'm lobbying to let the SolrDispatchFilter handle /select. The
SolrDispatchFilter passes the error code and message on to the servlet
container so it is formatted in the most standard way. It also only
includes a stack trace for 500 errors, not 400,403,etc. It uses:
res.sendError( code, ex.getMessage() );
ryan
