Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
MapQuest uses slightly different hostnames for HTTP and HTTPS access to its map tiles. This patch adds support for the HTTPS hostnames so MapQuest works on Drupal sites using HTTPS.
Comment | File | Size | Author |
---|---|---|---|
#4 | mapquest-https.png | 608.18 KB | Pol |
openlayers-mapquest-https.patch | 2.84 KB | mfb | |
Comments
Comment #1
filburt CreditAttribution: filburt commentedThanks a lot! Works like a charme!
Greetings, Filburt
Comment #2
PolThanks, patch committed.
Comment #3
filburt CreditAttribution: filburt commentedIt seems that the patch does not work in Chrome - no map is shown :-( In other browsers it works perfectly...
Cheers, Filburt
Comment #4
PolI couldn't reproduce the bug, and it's working good, even in https.
See the attached screenshot.
Comment #6
filburt CreditAttribution: filburt commentedSorry, but I still have the issue - could you please check the following URL in Firefox vs. Chrome?
https://arche-nova.org/en/countries/burkina-faso
Thanks a lot for support!
PS.: If I deactivate SSL everything works fine.
Comment #7
andros CreditAttribution: andros commentedAs for MapQuest the generated links to the actual map images are eg.:
//otile4.mqcdn.com/tiles/1.0.0/osm/3/4/3.png
As the http version of this is functioning as expected it is translated on https sites to:
https://otile4.mqcdn.com/tiles/1.0.0/osm/3/4/3.png
But *.mqcdn.com has no valid certificate for these sub domains and also I get an error message (chromium on linux) if i click to ignore the broken cert.
I have seen browsers and / or different OSs react different to that, but in most cases it didn't show any thing of the map.
Conclusion: at least the MapQuest layer is broken because of this problem.
Even with Google maps I have had sometimes problems on https sites, but by now I have no idea what the exact reason was, o I leave it by that.
As this can really be a destructive problem on https sites and Drupal offers support for https, I consider this as major.
Comment #8
PolHi,
Could you provide a patch so we can fix this ?
thanks !
Comment #8.0
Polspelling correction
Comment #9
mcdruidJust came across this issue on a site using the mapquest_osm layer.
In this case, the fix turned out to be as simple as reverting the layer to Default state (as opposed to Overridden) so that the code which switches the mapquest URLs based on the value of the $is_https global actually runs. If the layer is overridden the settings get saved to the db, and URLs won't switch.
If you have customisations to the layer and can't revert it to Default, you'd need to manually edit the mapquest URLs so that they have the correct hostname.
I'm pretty sure the https support works fine as long as the code is actually running, so I'm going to set this issue back to Closed (fixed).
Comment #10
jwilson3reverting the osm mapquest map back to the default (per #9) fixed the problem for me as well. Thanks @mcdruid.