Hi, Our proxy does not require user/password but these options work for the server/port part:
1) Set environmental variable and run gdalinfo SET https_proxy=our_proxy.fi:8888 gdalinfo "WMS:https://www.idee.es/wms/PNOA/PNOA?service=wms&request=getcapabilities"; 2) Set proxy with config option gdalinfo "WMS:https://www.idee.es/wms/PNOA/PNOA?service=wms&request=getcapabilities"; --config gdal_http_proxy our_proxy.fi:8888 Config option gdal_http_proxy seems to work also with https. Environmental variables must be set explicitly for http_proxy and https_proxy. And --config can be repeated. Which method to use depends on your work environment. I believe that technically the options are identical but if you use both internal and external services which require different proxy settings it might be more clear to define the proxy with config option. -Jukka Rahkonen- Elena Ruiz wrote: > Hello, I need to access the information from a WMS server through a proxy. I > would need to > know exactly the syntax to use the proxy, I have tried the following: > gdalinfo > "WMS:https://www.idee.es/wms/PNOA/PNOA?service=wms&request=getcapabilities"; > -config GDAL_HTTP_PROXY xx.xxx.x.xx:3128 -config GDAL_HTTP_PROXYUSERPWD > user:password -config GDAL_HTTP_AUTH NTLM > Would it be okay with the previous syntax? Can you repeat the word --config? > Do you need > quotes or brackets for the IP: port or user: password? in the case of > GDAL_HTTP_AUTH, > how to know whether to put NTLM or BASIC? and finally, is it better to put > the parameters > after gdalinfo or in the system variables? > I'm waiting for your answer, regards _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
