lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-1123) Change the JSONResponseWriter content type
Date Sun, 02 Oct 2011 23:20:33 GMT


Yonik Seeley commented on SOLR-1123:

The downside for the small minority of users likely to have a browser JSON plugin installed
is that they will still see a text JSON response.  This is a much more graceful fallback,
and we can add an optional parameter to change the content-type.  It seems pretty clear to
me that the default content-type should remain as is for the best user experience for the
majority of new users.  I originally coded the content-type as something with x-json in it
(Solr's JSON support pre-dates the RFC), but sending a query to solr and being prompted to
download the reply or search the internet for a plugin is horrible and will definitely turn
people off.

And don't get me started on the overreaching JSON RFC wrt specifying encodings.
> Change the JSONResponseWriter content type
> ------------------------------------------
>                 Key: SOLR-1123
>                 URL:
>             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|]
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|])
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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message