[Gdal-dev] Method to get a google image by url?

Garrett Potts potts at cfl.rr.com
Thu Nov 15 10:12:37 EST 2007


This is a cut and paste from the libcurl docs on setting a proxy  
through the environment if the program doesn't expose it for ya to set.



the environment variable is http_proxy and they describe the format  
of it here



Take care



Garrett





libcurl automatically checks and uses a set of environment variables  
to know what proxies to use for certain protocols. The names of the  
variables are following an ancient de facto standard and are built up  
as "[protocol]_proxy" (note the lower casing). Which makes the  
variable 'http_proxy' checked for a name of a proxy to use when the  
input URL is HTTP. Following the same rule, the variable named  
'ftp_proxy' is checked for FTP URLs. Again, the proxies are always  
HTTP proxies, the different names of the variables simply allows  
different HTTP proxies to be used.

The proxy environment variable contents should be in the format  
"[protocol://][user:password@]machine[:port]". Where the protocol://  
part is simply ignored if present (so http://proxy and bluerk://proxy  
will do the same) and the optional port number specifies on which  
port the proxy operates on the host. If not specified, the internal  
default port number will be used and that is most likely *not* the  
one you would like it to be.

There are two special environment variables. 'all_proxy' is what sets  
proxy for any URL in case the protocol specific variable wasn't set,  
and 'no_proxy' defines a list of hosts that should not use a proxy  
even though a variable may say so. If 'no_proxy' is a plain asterisk  
("*") it matches all hosts.

To explicitly disable libcurl's checking for and using the proxy  
environment variables, set the proxy name to "" - an empty string -  
with CURLOPT_PROXY.





http://curl.haxx.se/libcurl/c/libcurl-tutorial.html


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20071115/d082d70b/attachment.html


More information about the gdal-dev mailing list