Doug, Thanks for bringing this up. This fix doesn't address the scheme configuration. You will still need to do the change in container.js to get around the problem... Please try following two configuration: "defaultShindigTestHost":"http://%authority%";, or "defaultShindigTestHost":"//%authority%",
I'd be happy to extend the patch to handle scheme automatically from request as well... However schemeless url seems to be another alternative. is there any reason we couldn't remove the scheme here? thanks! li From: daviesd <[email protected]> To: "[email protected]" <[email protected]> Date: 06/14/2011 11:28 AM Subject: SHINDIG-1541 Thank Li/Paul for the SHINDIG-1541. I¹m still having an issue however. It¹s not using the protocol (http/https). So if my shindig server is running as https I was hoping it would return a iframe url something like this https://myshindigserver:8443/shindig/gadgets/ifr?url= But instead it returns http://myshindigserver:8443/shindig/gadgets/ifr?url= Before this fix I was getting around this by overriding the unlockedDomain container.js value in my own container-https.js "gadgets.uri.iframe.unlockedDomain" : "https://${SERVER_HOST}:${SERVER_PORT}"; And specifying shindig.host and shindig.port in my system properties. But I¹d really like to get away from this. Ideas? Was this fix meant to understand protocol? Thanks, Doug
