<div dir="auto"><div dir="auto">If your GeoMoose (or other web map) is hosted on https but you are displaying tiles or WMS maps over http, the browser will complain (sometimes quietly) that the page isn't secure because some elements of the page were loaded over http and could have possibly be tampered with (say to insert javascript).</div><div dir="auto"><br></div><div dir="auto">Not necessarily a GeoMoose proper concern, but I also have sites that are enforcing https so they can use the geolocation API. Thus those sites also require tiles/WMS over https.</div><div dir="auto"><br></div><div dir="auto">My experience with (MapServer) WMS over https is it works without issue for both web maps and the usual desktop applications.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Feb 6, 2017 2:28 PM, "Brent Fraser" <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Eli,<br>
<br>
Yes it can. I don't recall doing anything special to mapserver or mapcache to enable https. And all Geomoose needs is a map-source url starting with https.<br>
<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 2/6/2017 11:53 AM, Eli Adam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
slightly off-topic: This is more of a MapServer question but relates<br>
to GeoMoose as a client too. Can MapServer serve WMS/WFS over https?<br>
I've not found it in the docs or email lists (but my searching may be<br>
at fault).<br>
<br>
Best regards, Eli<br>
<br>
On Mon, Feb 6, 2017 at 10:39 AM, Jeff McKenna<br>
<<a href="mailto:jmckenna@gatewaygeomatics.com" target="_blank">jmckenna@gatewaygeomatics.com</a><wbr>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Brent,<br>
<br>
MS4W includes an important file for this, the CA certificate bundle, and<br>
Apache's httpd.conf points to it (see<br>
<a href="http://ms4w.com/README_INSTALL.html#k-certificates-for-https-with-wms-wfs-servers" rel="noreferrer" target="_blank">http://ms4w.com/README_INSTALL<wbr>.html#k-certificates-for-<wbr>https-with-wms-wfs-servers</a>).<br>
However sometimes MS4W gets upgraded and that little file is forgotten in<br>
the release package (I believe this was missing in MS4W 3.1.4); the file is<br>
included in the recent MS4W 3.2.0 release. But if you ever notice anything<br>
missing in an MS4W, please file a ticket right away on that at<br>
<a href="http://ms4w.com/trac" rel="noreferrer" target="_blank">http://ms4w.com/trac</a> (otherwise that little file will be missed in the next<br>
release).<br>
<br>
-jeff<br>
<br>
<br>
<br>
On 2017-02-05 10:45 PM, Brent Fraser wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
To get identify.php to work when I specify a WMS map-source using<br>
https (instead of the old and out-dated http), I had to add a couple of<br>
curl options to identify.php around line 196:<br>
<br>
curl_setopt($curlHandle, CURLOPT_SSL_VERIFYHOST, 0);<br>
curl_setopt($curlHandle, CURLOPT_SSL_VERIFYPEER, 0);<br>
<br>
Should I file an issue or is this already handled in 3.0?<br>
<br>
And what's with hardcoding "INFO_FORMAT=application/vnd.o<wbr>gc.gml" into<br>
the request? Should we make that configurable in the map-source<br>
definition?<br>
<br>
Thanks!<br>
<br>
</blockquote>
<br>
--<br>
Jeff McKenna<br>
MapServer Consulting and Training Services<br>
<a href="http://www.gatewaygeomatics.com/" rel="noreferrer" target="_blank">http://www.gatewaygeomatics.co<wbr>m/</a><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-users</a><br>
</blockquote>
______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-users</a><br>
</blockquote>
<br>
<br>
______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-users</a></blockquote></div></div>