Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 40415 invoked from network); 22 Apr 2009 12:19:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Apr 2009 12:19:18 -0000 Received: (qmail 47433 invoked by uid 500); 22 Apr 2009 12:19:17 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 47371 invoked by uid 500); 22 Apr 2009 12:19:17 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 47361 invoked by uid 99); 22 Apr 2009 12:19:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 12:19:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 12:19:07 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8F148234C041 for ; Wed, 22 Apr 2009 05:18:47 -0700 (PDT) Message-ID: <1518456219.1240402727584.JavaMail.jira@brutus> Date: Wed, 22 Apr 2009 05:18:47 -0700 (PDT) From: "Uri Boness (JIRA)" To: solr-dev@lucene.apache.org Subject: [jira] Created: (SOLR-1123) Change the JSONResponseWriter content type MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Change the JSONResponseWriter content type ------------------------------------------ Key: SOLR-1123 URL: https://issues.apache.org/jira/browse/SOLR-1123 Project: Solr Issue Type: Improvement Affects Versions: 1.3 Reporter: Uri Boness Fix For: 1.3.1 Currently the jSON content type is not used. Instead the palin/text content type is used. The reason for this as I understand is to enable viewing the json response as as text in the browser. While this is valid argument, I do believe that there should at least be an option to configure this writer to use the JSON content type. According to [RFC4627|http://www.ietf.org/rfc/rfc4627.txt] the json content type needs to be application/json (and not text/x-json). The reason this can be very helpful is that today you have plugins for browsers (e.g. [JSONView|http://brh.numbera.com/software/jsonview]) that can render any page with application/json content type in a user friendly manner (just like xml is supported). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.