Hi Doug, Sounds like you might have an opensocial endpoint hard-coded to HTTP -- random guess. What browser are you using? I'd give Chrome a try and see what the Network tab says, to see if a request is being formulated.
--j On Fri, Mar 25, 2011 at 11:12 AM, Doug Ellison <[email protected]>wrote: > I'm running Apache Shindig within a webapp and it seems to work > fantastic in most respects but I'm having one difficulty that I've > spent more then a few days on trying to figure out. > > When I make a call such as > > http://localhost/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml > it renders and works. Also if I do > > https://localhost/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml > it renders and works. I've written a gadget that has the following > calls > > function request() { > DisplayHTML("<h1> Loading...</h1>"); > var viewerIdSpec = opensocial.newIdSpec({userId: 'VIEWER'}); > var req = opensocial.newDataRequest(); > > req.add(req.newFetchPersonRequest('VIEWER'), 'viewer'); > req.add(req.newFetchPersonAppDataRequest(viewerIdSpec, > "*"), "viewer_data"); > > req.send(handleRequest); > } > > Here is where my problem begins. If I put my gadget within http:// it > works just fine and as expected. When I add https:// the method for > handling the response never gets called. So it seems to be a > problem within routing between http and https but only with certain > gadgets. However I can't seem to find a configuration option or don't > understand enough to know whats really happening. Any help would be > greatly appreciated. >
