You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Henry Saputra (JIRA)" <ji...@apache.org> on 2011/03/23 20:26:06 UTC
[jira] [Assigned] (SHINDIG-1515) Why shindig uses "Content-Type"
not "Accept" to determine the return info type
[ https://issues.apache.org/jira/browse/SHINDIG-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Saputra reassigned SHINDIG-1515:
--------------------------------------
Assignee: Henry Saputra
> Why shindig uses "Content-Type" not "Accept" to determine the return info type
> ------------------------------------------------------------------------------
>
> Key: SHINDIG-1515
> URL: https://issues.apache.org/jira/browse/SHINDIG-1515
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.2
> Reporter: hongtao
> Assignee: Henry Saputra
>
> I checked the shindig code(common org.apache.shindig.protocol.DataServiceServlet), which is used to handle opensocial REST call.
> The type of response is determined by "Content-Type" header, not "Accept" header.
> From reading of http1.1(Content-Type : http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17, Accept : http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1),
> my understanding is,
> The "Content-Type" is used by server to tell the receiver the type of response, when it is added to response.
> The "Accept" is used by request sender to tell server the type of response he expecting, when it is in request.
> The "Content-Type" in request should be used to tell server the type of request's content.
> Is this a bug of shindig that it utilizes "Content-Type" not "Accept" to decide the response type?
> Or if there is any doc specifies this behavior, please send me the link.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira