-
Posts
-
I am getting the following error message on my site:
“The Google Maps API server rejected your request. Requests to this API must be over SSL.”
I have the Google Map shortcode for the “header widget area 2” and also on my contact page. How do I resolve this issue?
This reply has been marked as private.Hi Benjamin!
Thank for using the theme!
Regretfully, at this time I am not entirely certain what’s the issue. We’ll be happy to provide you with a response once we have a better understanding of the situation. This is usually cause by a plugin conflict so if you have any plugins that you added recently, please try to deactivate them for testing.
I narrowed it down to the WordPress HTTPS plugin (Version 3.3.6). I need this plugin because I recently added an SSL certificate to my apply online page to added an extra level of security since I am collecting clients personal information.
That is the only page that I need to be https: and this is the plugin that everyone recommends unless you know of a better way so that it doesn’t conflict with the X google maps api shortcode.
Hi Ben,
Glad you found the culprit! Fixing this is a bit outside the scope of support we can offer, but I can certainly get ou pointed in the right direction.
When using the HTPPS plugin, you’ll need a way to exlude “https://www.google.com/maps” URLs from being filtered.
The plugin author has some advice here: http://wordpress.org/support/topic/fully-ssl-enabled-site-ok-wexception-of-feedburner?replies=7
I reviewed this link and I’m not quite sure how it applies to my issue. I did some additional research and wouldn’t it be more efficient to use a protocol relative url? I was going to test this by trying to find the google maps api within the framework but couldn’t find what folder it was located in.
Would this work and if so, what folder is it located in?
Benjamin,
The problem is is that we’re adding a Google Maps iFrame to the page. When this is added, it’s done with an HTTPS URL, which is correct. The Google Maps API won’t server anything over standard HTTP.
The problem is that your HTTPS plugin is catching this, and reverting the URL back to HTTP because it’s trying to match the protocol being used on your contact page, which is https
Modifying the google maps code won’t make a difference because the HTTPS plugin is still going to filter the URL.
You’ll need to modify that plugin to avoid Google Maps, or implement a workaround similar to the one advised on that thread.
You could also try adding your contact page as an exception for the HTTPS plugin. At this point, the entire page would be served over HTTPS which may not be desired.
