Mixed Content: The page at 'https://sitename.com/abc/def' was loaded over HTTPS, but requested an insecure script 'http://maps.googleapis.com/maps/api/js?v=3.exp&libraries=places&sensor=false'. This request has been blocked; the content must be served over HTTPS
The browser will load with the correct protocol. This goes for images as well. Then if the user comes from http, it will load http, https if https.
How to Fix the Problem
If the problem appears on regular HTTPS secured pages with content that is being loaded via the insecure HTTP protocol, you can control how the content behaves.
Links with “http://” extensions need to change to contain the “s” part of HTTP protocol (https://) pointing out to an SSL-reserved port. A more elegant way of handling different protocols is to have only slashes where port is expected “//”. so that page can use the protocol used to open the page itself: