Uploading a KMZ file on an HTTPS website using the Google Maps API v3, but overlaying images that a KMZ file is called through HTTP, Google

Question

As the name says, I have a KMZ file that loads well in the Google Maps API V3, but the images found in the KMZ file are called via HTTP, but I have HTTPS.

The API script is called via HTTPS, and even the KMZ URL is an HTTPS link. But then, when the API calls the image files found in the KMZ file, it calls the HTTP link below: http://maps.google.com/mapsatt?id=xxxxxxxxxx&f=files/xxxxxx.png&token=

This causes warnings about insecure content in browsers and prevents people with IE8 from viewing the google map. Is there a solution to this problem, because all I can think of so far is to use KML files to specify URLs themselves.

Answer 1

Thank you for noticing this. This should now work with https images. Please comment if this is not so.