[
https://issues.apache.org/jira/browse/SHINDIG-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065418#comment-14065418
]
Sunil Sasidharan Nair commented on SHINDIG-1971:
------------------------------------------------
Thanks Stan, It worked when I changed gadgets.uri.iframe.unlockedDomain value
in container.js to https,
But my application should support both http and https
how can i dynamically change value of gadgets.uri.iframe.unlockedDomain based
on the application that loads gadget .
ie if my application is loaded in http mode it should call
http://sciverse-shindig.elsevier.com/gadgets/js/core:rpc.js?container=default&nocache=1&debug=0&c=0
if my application is called in https mode it should call
https://sciverse-shindig.elsevier.com/gadgets/js/core:rpc.js?container=default&nocache=1&debug=0&c=0
can container .js values be overriden based on the request.
> Gadgets are not rendering for Https request
> -------------------------------------------
>
> Key: SHINDIG-1971
> URL: https://issues.apache.org/jira/browse/SHINDIG-1971
> Project: Shindig
> Issue Type: Question
> Components: Java
> Affects Versions: 2.0.0
> Environment: Linux and windows
> Reporter: Sunil Sasidharan Nair
> Labels: blocking, https, mixedcontent
>
> Our application was supporting only http, gadgets where getting rendered in
> Iframe without any issues using Shindig version 2.0, we have a new
> requirement to support https , as part this we made sure all the js, css,
> images that where internally called within gadget was changed to https, but
> still gadgets are not getting rendered within Iframe since some of the
> internal shindig api call like rpc calls are still in http and these are
> getting blocked.
> http://sciverse-shindig.elsevier.com/gadgets/js/core:rpc.js?container=default&nocache=1&debug=0&c=0
> Can you please guide us in resolving this issue ,
> Migrating to newer version of shindig server will it resolve this issue
--
This message was sent by Atlassian JIRA
(v6.2#6252)
