Dantzler, DeWayne C wrote:
But I did set the http_proxy variable from the UNIX command as follows: export
http_proxy=www.myproxyHost:port
So why do you use curl_easy_setopt then?
And I did configure Xerces to use the curl netaccessor according to the Xerces
documentation. The config.log file confirmed this and I've included it below.
So, why is Xerces using the SocketNetAccessor instead of the curlNetAccessor?
How do you confirm that the build phase indeed built Xerces with the curl
NetAccessor? Is there a build log to check?
You should look for this lines in your make log:
============================================================
Compiling xercesc/util/NetAccessors/Curl/CurlNetAccessor.cpp
Compiling xercesc/util/NetAccessors/Curl/CurlURLInputStream.cpp
============================================================
Good luck!
Vitaly
