lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (SOLR-1123) Change the JSONResponseWriter content type
Date Sun, 02 Oct 2011 07:24:34 GMT

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

Chris Male edited comment on SOLR-1123 at 10/2/11 7:23 AM:
-----------------------------------------------------------

I agree with Chris wholeheartedly.  

It doesn't seem to be user-friendly to return a content-type that isn't inline with the RFC
standard and I can't help but feel that the number of users who will be negatively impacted
by this change will be small.  Those users can then either use XML or some other text format,
or install a JSON plugin for their browser.

There's a reason this keeps coming up in discussion.

Chris, can you put together a patch which changes the content-type?
                
      was (Author: cmale):
    I agree with Chris wholeheartedly.  

It doesn't seem to be user-friendly to return a content-type that isn't inline with the RFC
standard and I can't help but feel that the number of users who will be negatively impacted
by this change will be small.

There's a reason this keeps coming up in discussion.

Chris, can you put together a patch which changes the content-type?
                  
> 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: 3.5, 4.0
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message