[SHINDIG-1619] Proxied content broken for Content sections using href

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0.2
• Component/s: Java
• Labels: opensocial proxied_content
• Environment: All
• Assignee: Henry Saputra
• Reporter: Mark Weitzel
• Created: 09/Sep/11 14:10
• Updated: 28/Oct/11 23:29
• Resolved: 28/Oct/11 23:23

Description

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).