[
https://issues.apache.org/jira/browse/SHINDIG-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348371#comment-14348371
]
Tran The Trong commented on SHINDIG-1993:
-----------------------------------------
I do think the host and scheme both should be substituted with the current ones.
I find we can remove the scheme from many URI configuration in other parts in
container.js without any problem. BTW, there is a similar issue SHINDIG-1884
which has been fixed.
> Remove hardcode scheme for opensocial-data pipline feature configuration
> ------------------------------------------------------------------------
>
> Key: SHINDIG-1993
> URL: https://issues.apache.org/jira/browse/SHINDIG-1993
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.0.2
> Reporter: Phuong
>
> In container.js, we find this config:
> {code}
> "gadgets.osDataUri" : "http://%host%/social/rpc";
> {code}
> The "http" scheme is hardcode like that, that prevent us to use https, if we
> try to remove the hardcode scheme, it show exception on shindig server when
> using the feature
> {code}
> <ModulePrefs>
> <Require feature="opensocial-data"/>
> </ModulePrefs>
> <Content type="html"><![CDATA[
> <script xmlns:os="http://ns.opensocial.org/2008/markup"; type="text/os-data">
> <os:DataRequest key="vwr" method="people.get" userId="@viewer"
> fields="name,birthday"/>
> <os:ViewerRequest key="vwr2" fields="name,birthday"/>
> <os:HttpRequest key="mydata" href="http://example.com/api"/>
> </script>
> ... HTML content here ...
> ]]></Content>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
