The bad news is that you use the Google Maps - SSL API , you still sometimes get a Secure and Unsecured warning. That's why:
The Google url above displays everything under https: // to display the secure environment correctly. However , this is a huge problem . Google now displays an image of the building or location on the left in without https , which gives us a "strong" unsecured error that we hate to get in a secure environment.
Here is a good example ... take a look at the following:
https://maps-api-ssl.google.com/maps?q=1000+Ballpark+Way,+Arlington,+TX&hl= en & SLL = 37.0625, -95.677068 & sspn = 49.310476,101.425781 & vpsrc = 0 & hnear = 1000 + Ballpark + Way + Arlington + Texas + 76011 & t = m & g = 17
Now, using Firefox or the browser of your choice, right-click on the image of the building Info or Image Properties ... and WOW! You will see that this image causes your unsecured error when everything that matches Google needs to be protected for https: //
Images of the building and location are not listed in https: // .... you will still receive an error message!
Check it out for yourself and you will see what I see ... so viewing Google maps for SSL is still a problem if someone does not know about the work round, to delete this location or images of buildings or to display for https : //, but not http: //, for example, in the case of the image itself.
Bottom line ... it's still a problem due to non -SSL photo images ...
Check it out and you'll see what I'm talking about.
If anyone knows about this, I would definitely like to know. Google, if you have an explanation, please let us know.