You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "David Citron (JIRA)" <ji...@apache.org> on 2008/10/29 04:10:44 UTC

[jira] Updated: (SHINDIG-665) Content-type not set for JSON responses

     [ https://issues.apache.org/jira/browse/SHINDIG-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Citron updated SHINDIG-665:
---------------------------------

    Attachment: shindig-665.patch

I've attached a patch that I tried, and it resolved the FF errors for me, but a more experienced Shindig developer may see issues with my patch or other areas that it should apply to.

> Content-type not set for JSON responses
> ---------------------------------------
>
>                 Key: SHINDIG-665
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-665
>             Project: Shindig
>          Issue Type: Bug
>          Components: RESTful API (Java)
>         Environment: Firefox 3
>            Reporter: David Citron
>            Priority: Minor
>         Attachments: shindig-665.patch
>
>
> Currently, the "Content-Type" response header is not being set for JSON
> responses from, for example, DataServiceServlet and JsonRpcServlet. As
> such, the JSON data returned is causing errors to appear in the FireFox
> "Error Console" (syntax error/not well-formed). These errors do not
> appear to have any adverse effects on the browser behavior (?) but they
> do make gadget development more difficult as these spurious errors must
> be ignored.
> Is there a reason why DataServiceServlet and JsonRpcServlet don't set
> the response content type, similar to RpcServlet?
>    servletResponse.setContentType("application/json; charset=utf-8");

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