[
https://issues.apache.org/jira/browse/SOLR-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770860#action_12770860
]
Shalin Shekhar Mangar commented on SOLR-1528:
---------------------------------------------
Possible solutions in case of error:
# Send a binary payload with HTTP 200 OK and no-cache headers
# Send an XML payload in the response
# Any other?
We tried #2 but ran into another problem. The default version for javabin is
1.0 whereas for xml is 2.3. But if we start writing XML payload on error, then
XMLResponseWriter uses javabin's version (1.0) which corresponds to the older
XML format (which is again unparseable by the solrj client).
> A non-200 response code gives no response body with wt=javabin
> --------------------------------------------------------------
>
> Key: SOLR-1528
> URL: https://issues.apache.org/jira/browse/SOLR-1528
> Project: Solr
> Issue Type: Bug
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.5
>
>
> Servlet Engines (Tomcat & Jetty) do not allow you to write binary payload
> when the HTTP response code is not 200. Therefore, when an error occurs
> during a request and wt=javabin then although the response to the client has
> the correct HTTP response code (4xx/5xx), it has no binary payload. Instead,
> tomcat sends out a character stream with stack traces which causes an
> exception in the clients because they were expecting a binary payload.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
