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.

#4 mapquest-https.png608.18 KBPol
openlayers-mapquest-https.patch2.84 KBmfb
Members fund testing for the Drupal project. Drupal Association Learn more


filburt’s picture

Thanks a lot! Works like a charme!

Greetings, Filburt

Pol’s picture

Status: Needs review » Fixed

Thanks, patch committed.

filburt’s picture

It seems that the patch does not work in Chrome - no map is shown :-( In other browsers it works perfectly...

Cheers, Filburt

Pol’s picture

608.18 KB

I couldn't reproduce the bug, and it's working good, even in https.

See the attached screenshot.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

filburt’s picture

Sorry, but I still have the issue - could you please check the following URL in Firefox vs. Chrome?

Thanks a lot for support!

PS.: If I deactivate SSL everything works fine.

andros’s picture

Priority: Normal » Major
Status: Closed (fixed) » Active

As for MapQuest the generated links to the actual map images are eg.:


As the http version of this is functioning as expected it is translated on https sites to:

But * 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.

Service Unavailable
The server is temporarily unable to service your request. Please try again later.
Reference #6.144a9f3e.1377946013.9e13798

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.

Pol’s picture

Status: Active » Needs work


Could you provide a patch so we can fix this ?

thanks !

Pol’s picture

Issue summary: View changes

spelling correction

mcdruid’s picture

Issue summary: View changes
Status: Needs work » Closed (fixed)

Just 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).

jwilson3’s picture

reverting the osm mapquest map back to the default (per #9) fixed the problem for me as well. Thanks @mcdruid.