Comment by paulproteus:
<lfaraone> paulproteus: hai!
<lfaraone> paulproteus: fyi, on openhatch, my browser is giving SSL warnings
because there are mixes of SSL and non-ssl content
If you load up https://openhatch.org/ in Firefox, and use Firebug to look at the
"Net" tab to see what pages we load, it should be all SSL ones. According to
Luke, it's not all SSL stuff -- that's the bug.
Comment by jesstess:
could use a reverse proxy to achieve that.
If we were a 501(c)3, we could request a free Premier key for Google Maps. It
would take 3 months for Google to contact us about it.
https://services.google.com/fb/forms/premiergrantapplication/ is the link to that.
Well, what now? I was hoping this would be easy, but I guess it's not!
indicates that we might be able to get away with using a redirect, rather than
Chromium still shows https crossed-out, and Firefox doesn't show the nice blue
domain that indicates it's happy with the SSL setup, so I conclude that
redirects can't help.
Reverse proxies can't really help either -- once the browser grabs the initial
haven't found any information on getting Google Maps to load tiles from our
server, rather than theirs.
So, um, I guess HTTPS and the Google Maps API are quite at odds.
Not terribly useful, but nice to know we're not alone.
Decide to do nothing, and leave the warning. That's probably bad.
Pay $10K. (not happening, unless someone else really wants to spend it on this)
Decide to proxy the tiles. (This is more reasonable than it sounds; for one
thing, we're only at 10% of our monthly bandwidth usage.) I think this is what
we should go with, for now.
Decide to, for all people search pages, redirect the user to an http-based
security and privacy.)
So let's decide to proxy the tiles. Next step is to figure out how that'll work.
That'll be a separate ticket.
Comment by palhmbs:
There is a new issue to deal with implementing that. - See issue344.
Nosy List: jesstess, paulproteus
Imported from roundup ID: 213 (view archived page)
Last modified: 2011-03-24.18:53:45