If you've got a good argument for making https available with a free API key, then you can add a comment to issue 591.
http://code.google.com/p/gmaps-api-issues/issues/detail?id=591 That enhancement issue exists for the purpose of tracking interest in extending https access to free Maps API sites. I can see why Google might not want to implement that enhancement. The availability of https with a free key might increase the number of sites that illegally run the free API on pages that are not publicly accessible, thus reducing their income from Premier and Enterprise fees. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
