That makes sense -- that's essentially what I mean when I say there are some places where config and URL validation could use some cleanup to be schema-agnostic. Best is schema-relative, but the difficulty w/ that is that you need (in server code) to inject schema in various places.
--j On Fri, Mar 25, 2011 at 4:49 PM, Doug Ellison <[email protected]>wrote: > I guess what I'm referring to for transitions is I access servlets from > https and they are accessible. But checking chrome javascript logs there > are still references to http and those references are what seem to break. > So transition is probably not the right word. It doesn't always detect from > where it came http or https and always use the correct pathing. Does that > make sense? I guess I wilk try doing a replace all from http to https and > see what happens. > > On Mar 25, 2011 5:37 PM, "John Hjelmstad" <[email protected]> wrote: > > 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 t... > >
