[ https://issues.apache.org/jira/browse/SOLR-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904275#action_12904275 ]
Chris Tucker commented on SOLR-1123: ------------------------------------ I'd like to +1 the short-term fix. The incorrect content type makes it difficult to filter/transform the response in a servlet filter or Jetty handler: one has to inspect the wt parameter on the request to establish (guess?) that JSON has been requested and is being sent back. > Change the JSONResponseWriter content type > ------------------------------------------ > > Key: SOLR-1123 > URL: https://issues.apache.org/jira/browse/SOLR-1123 > Project: Solr > Issue Type: Improvement > Reporter: Uri Boness > Fix For: Next > > Attachments: JSON_contentType_incl_tests.patch > > > 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. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org