Title: HTTPS support
Last modified: August 22, 2016

---

# HTTPS support

 *  [tinuzz](https://wordpress.org/support/users/tinuzz/)
 * (@tinuzz)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/https-support-20/)
 * Hi,
 * I run a WP instance on a HTTPS URL and I noticed that GPXpress has a few issues
   when running under HTTPS.
 * First: the URLs for the Leaflet JS and CSS are hardcoded to [http://](https://wordpress.org/support/topic/https-support-20/?output_format=md),
   so modern browsers will refuse to load these scripts as ‘unsafe’. Changing the
   URLs and leave out the protocol (//cdn.leafletjs.com/…) would be a solution, 
   if it weren’t for the second issue, being that cdn.leafletjs.com doesn’t properly
   support HTTPS, it serves a certificate for another domain
 * You would have to consider importing the script and CSS from somewhere else, 
   for example:
 * //cdnjs.cloudflare.com/ajax/libs/leaflet/0.7.3/leaflet.js
    //cdnjs.cloudflare.
   com/ajax/libs/leaflet/0.7.3/leaflet.css
 * Hope this helps.
 * [https://wordpress.org/plugins/gpxpress/](https://wordpress.org/plugins/gpxpress/)

The topic ‘HTTPS support’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gpxpress.svg)
 * [GPXpress](https://wordpress.org/plugins/gpxpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gpxpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gpxpress/)
 * [Active Topics](https://wordpress.org/support/plugin/gpxpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gpxpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gpxpress/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [tinuzz](https://wordpress.org/support/users/tinuzz/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/https-support-20/)
 * Status: not resolved