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 d
: If the front application calls Solr with /select but missing q parameter,
: Solr returns a stack trace with its response body, while we expect
: XML response with an error message (& the stack trace in the XML).
: Is it a feature?
:
: If so, is the front server responsible about checking require
Hello,
We have a front application server that uses Solr to search our contents.
If the front application calls Solr with /select but missing q parameter,
Solr returns a stack trace with its response body, while we expect
XML response with an error message (& the stack trace in the XML).
Is it a
