lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1528) A non-200 response code gives no response body with wt=javabin
Date Thu, 29 Oct 2009 01:14:59 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771237#action_12771237
] 

Yonik Seeley commented on SOLR-1528:
------------------------------------

This doesn't seem unique to the binary format...
We don't currently return parseable errors for any return format do we?

{code}
$ curl 'http://localhost:8983/solr/select?q=foo:bar&wt=json'
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 400 </title>
</head>
<body><h2>HTTP ERROR: 400</h2><pre>undefined field foo</pre>
<p>RequestURI=/solr/select</p><p><i><small><a href="http://jetty.mortbay.org/">P
owered by Jetty://</a></small></i></p><br/>
[...]
{code}


> 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.


Mime
View raw message