Can you test http://trac.osgeo.org/gdal/changeset/21304/trunk ? Add
<UnsafeSSL>true</UnsafeSSL> inside <GDAL_WMS>.
Jukka Rahkonen wrote:
Jukka Rahkonen <jukka.rahkonen <at> mmmtike.fi> writes:
We would like to use gdal_translate for reading fromn our WMS service
which is> secured by our own certificate and thus not automatically
trusted. Our developer had a quick look on a gdal source code and
tried to find how options CURLOPT_SSL_VERIFYPEER (1) and CURLOPT_CAPATH
(2) are used there. Numbers are referring to document
http://curl.haxx.se/docs/sslcerts.html
The conclusion was that those options are not used and thus it is
impossible to use dgal_translate with our server. Is this true, and
if yes, would it be worth filing a ticket?
We got help for our immediate need by making an own modified build. We opened
also a new ticket about fixing the thing permanently
(http://trac.osgeo.org/gdal/ticket/3882) because our developer wrote me
"Building gdal with curl for Windows is non-trivial".
-Jukka Rahkonen-
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
