When viewing the Google map layer, the map fails to visualise in Chrome browser using HTTPS protocol due to the file being blocked.
The issue is due to the URL (http://maps.google.com/maps?file=api), which does not respect the protocol being used by the users browser. So in this case, under HTTPS, the Google map file is forced to load using HTTP and Chrome sees it as being insecure so it is blocked.
This can be easily fixed by using a double backslash before the domain name (eg. //maps.google.com/maps?file=api) which then allows the browser to determine the appropriate protocol to use (HTTP or HTTPS), as per RFC 1808, Section 4
Patch attached.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | openlayers_layer_type_google.inc_.patch | 1.1 KB | johnnybgoode |
| openlayers_protocol.patch | 776 bytes | andrewsuth |
Comments
Comment #1
polThanks Andrew, committed to 6.x and already in 7.x ;-)
Comment #3
johnnybgoode commentedThis issue is not fixed as of 7.x-2.0-beta1. If you are experiencing this issue, see the attached patch and be sure to download openlayers.js and host your own copy (instructions at /admin/structure/openlayers) as openlayers.org is not ssl enabled and can't serve the library over https.
Comment #4
johnnybgoode commentedComment #5
polThis feature is in 7.x-2.x.
We usually do not provide patch for a tagged version like beta1, but for the dev version.