[jira] [Issue Comment Edited] (SHINDIG-1619) Proxied content broken for Content sections using href

["Henry Saputra (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SHINDIG-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138920#comment-13138920 ] 

Henry Saputra edited comment on SHINDIG-1619 at 10/28/11 11:29 PM:
-------------------------------------------------------------------

This is not repro with trunk. Send signed request to gadget:

<?xml version="1.0" encoding="UTF-8"?>
<Module>
    <ModulePrefs title="Test">
        <Require feature="dynamic-height"/>
        <Require feature="osapi"/>
        <Require feature="views"/>
        <Require feature="opensocial-data"/>
    </ModulePrefs>
    <Content authz="signed" view="home,canvas" type="html" href="http:/localhost/readPost.php" xmlns:os="http://ns.opensocial.org/2008/markup">
      <os:PeopleRequest key="vf" userId="@viewer" groupId="@friends" />
    </Content>
</Module>

got this as post body:

[{"id":"vf","result":{"filtered":false,"totalResults":3,"sorted":false,"list":[{"id":"jane.doe","name":{"formatted":"Jane Doe","familyName":"Doe","givenName":"Jane"}},{"id":"george.doe","name":{"formatted":"George Doe","familyName":"Doe","givenName":"George"}},{"id":"maija.m","name":{"formatted":"Maija Meikäläinen","familyName":"Meikäläinen","givenName":"Maija"}}],"updatedSince":false}}] 
                
      was (Author: hsaputra):
    This is not repro with trunk. Send signed request to gadget:

<?xml version="1.0" encoding="UTF-8"?>
<Module>
    <ModulePrefs title="Activities Reader Example" author="Jive Software">
        <Require feature="dynamic-height"/>
        <Require feature="osapi"/>
        <Require feature="views"/>
        <Require feature="opensocial-data"/>
    </ModulePrefs>
    <Content authz="signed" view="home,canvas" type="html" href="http:/localhost/readPost.php" xmlns:os="http://ns.opensocial.org/2008/markup">
      <os:PeopleRequest key="vf" userId="@viewer" groupId="@friends" />
    </Content>
</Module>

got this as post body:

[{"id":"vf","result":{"filtered":false,"totalResults":3,"sorted":false,"list":[{"id":"jane.doe","name":{"formatted":"Jane Doe","familyName":"Doe","givenName":"Jane"}},{"id":"george.doe","name":{"formatted":"George Doe","familyName":"Doe","givenName":"George"}},{"id":"maija.m","name":{"formatted":"Maija Meikäläinen","familyName":"Meikäläinen","givenName":"Maija"}}],"updatedSince":false}}] 
                  
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira