Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Message-ID: <30121616.18231282860294542.JavaMail.jira@thor>
Date: Thu, 26 Aug 2010 18:04:54 -0400 (EDT)
From: "Paul R. Brown (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-2091) wt=json is served as text/plain
In-Reply-To: <7215513.2121282815113569.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paul R. Brown commented on SOLR-2091:
-------------------------------------

Can we bump the other issue from improvement to bug, then?  The point is that this is something that will confuse folks who would like to write client code against Solr with standards-friendly tooling.

> wt=json is served as text/plain
> -------------------------------
>
>                 Key: SOLR-2091
>                 URL: https://issues.apache.org/jira/browse/SOLR-2091
>             Project: Solr
>          Issue Type: Bug
>          Components: Response Writers
>    Affects Versions: 1.4.1
>            Reporter: Paul R. Brown
>
> JSON data should be served as application/json.  SOLR-1123 is equivalent, except that I think that most people would regard serving JSON as text/plain as a bug.  If SOLR does serve content with a client-friendly type, then RESTful client frameworks can just do the right thing with responses.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org