You can still host gadgets on an HTTP server -- that's an orthogonal issue to the way that you access your Shindig-hosted server. Shindig acts as an HTTP client when fetching gadgets, and can fetch via HTTP or HTTPS.
What do you refer to when you say http/https transitions? For the most part Shindig supports HTTPS -- we @ Google use it extensively for this purpose. But there are a few bits and pieces of config/verification around that look like they could use some cleanup in the "default" installation to ensure HTTP/HTTPS agnosticism. --j On Fri, Mar 25, 2011 at 4:27 PM, Doug Ellison <[email protected]>wrote: > Thanks for all the info. One question that seems vague is can't i just run > everything from https without the need to transition between http and https > but still host the gadgets on a remote http > server? My main web app is hosted through jboss and I can access all the > servlets through https... Or atleast I thought. I think my problem stems > from shindig only partially supporting https and http transitions. Is my > understanding wrong? If I did a find replace all on http to https might > that fix it? > > On Mar 25, 2011 5:02 PM, "John Hjelmstad" <[email protected]> wrote: > > Good reminder. We should move that to a Shindig-based solution IMO. Anyone > able to volunteer? > > -j > > On Fri, Mar 25, 2011 at 3:59 PM, Niels van Dijk <[email protected] > >wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Another > headsup when using https ga... >
