aym / google-ajax-apis

Automatically exported from code.google.com/p/google-ajax-apis
0 stars 0 forks source link

The Google Maps API server rejected your request because you do not have permission to use this service over SSL. #519

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I am embedding jsapi on my website using ssl therefore i tried to include 
https://www.google.com/jsapi?key=mykey to make everything ssl to display ip 
adddress on the map and when click on the map,i got this error "The Google Maps 
API server rejected your request because you do not have permission to use this 
service over SSL".
I can fix it when i http://www.google.com/jsapi?key=mykey,not at https but on 
my site it would display some part of my site unencrypted so i would prefer 
jsapi at https.
Please help me out.
Thank you

Original issue reported on code.google.com by van.hie...@gmail.com on 21 Sep 2010 at 4:43

GoogleCodeExporter commented 8 years ago
The GMaps API is not accessible via SSL/HTTPS unless you pay for Maps Premiere 
access. For information about this, you can check out the link below:

http://www.google.com/enterprise/earthmaps/maps.html

The downside of this approach is that GMaps Premiere costs START at USD10,000 
per year and go up from there.

Original comment by jrgeer...@gmail.com on 21 Sep 2010 at 2:20

GoogleCodeExporter commented 8 years ago
Meant to do this with the last comment. Although I don't personally have 
insider information, I'm going to mark this as "Won't Fix" because it seems to 
be an integral part of Google's market strategy for the Maps API. If they 
decide to change that strategy at some point in the future, some Googler may 
want to revisit this issue.

Original comment by jrgeer...@gmail.com on 21 Sep 2010 at 2:22

GoogleCodeExporter commented 8 years ago
Is this bug still present?

If so, please remove the "WontFix" tag.  Isolating it and working out what to 
do about it caused a number of long-term headaches for HTTPS Everywhere project 
(https://www.eff.org/https-everywhere).  The problem is that we need to make 
sure that google.com/jsapi is *never* loaded over HTTP, because that leaves 
users vulnerable to a number of security problems.  But on a small subset of 
sites, that caused people to get an error message instead of a map:

https://trac.torproject.org/projects/tor/ticket/2335

I don't currently know a site where I can test for this bug, so I'm not sure if 
it's fixed or not.

Original comment by peter.ec...@gmail.com on 1 May 2011 at 8:17