[
https://issues.apache.org/jira/browse/SHINDIG-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Saputra reassigned SHINDIG-1619:
--------------------------------------
Assignee: Henry Saputra
> Proxied content broken for Content sections using href
> ------------------------------------------------------
>
> Key: SHINDIG-1619
> URL: https://issues.apache.org/jira/browse/SHINDIG-1619
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.2
> Environment: All
> Reporter: Mark Weitzel
> Assignee: Henry Saputra
> Priority: Critical
> Labels: opensocial, proxied_content
>
> The opensocial spec defines proxied content as follows:
> Data pipelining tags can be top level elements in the <Content> section of a
> gadget using Proxied Content (Section 6).
> Example
> <Content href="http://example.com/canvas";
> xmlns:os="http://ns.opensocial.org/2008/markup";>
> <os:PeopleRequest key="vf" userId="@viewer" groupId="@friends"/>
> </Content>
> When preparing a request for proxied content, a container MUST process data
> pipelining elements that are direct children of the proxied content's
> <Content> element. Data pipelining elements are ALWAYS valid when preparing a
> request for proxied content, even if the opensocial-data feature is not
> present.
> However, the gadget processing of the content elements do not process the os
> requests or the http request and therefore nothing get posted in the request
> to the home server specified in the href. (Note, these may be authz=signed to
> support 2-legged OAuth).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
