I've looked at the libcurl doc, but I'm using Xerces to parse and it is during the parsing of the XMl file that internet access occurs since the XML calls entities that must be resolved via a URL. Since Xerces can be configured with libcurl, my assumption is that somehow Xerces must use it. Given Alberto comments "If you use --enable-netaccessor-curl Xerces will use the APIs provided by libcurl, so if you use the same API to setup a global proxy, you will be able to use it." and based on the libcurl doc, my assumption is that setting the env 'http_proxy' using libcurl's API is how Xerces will know the correct proxy to use. Is this how Xerces will know the correct proxy to use?
-----Original Message----- From: Vitaly Prapirny [mailto:[email protected]] Sent: Thursday, November 05, 2009 12:18 AM To: [email protected] Subject: Re: What is the difference between configuring Xerces 3.0.1 with--enable-netaccessor-curlvs --enable-netaccessor-socket? Proxy settings should be recognized by libcurl, not Xerces. So please look at http://curl.haxx.se/libcurl/c/libcurl-tutorial.html as I suggest you in my answer to your previous message http://marc.info/?l=xerces-c-users&m=125541575925143&w=2 Good luck! Vitaly Dantzler, DeWayne C wrote: > Ok, If Xerces will use the APIs provided by libcurl, then what Xerces's APIs > must I use to get Xerces to recognize my proxy settings or how does Xerces > determine the proxy settings? I've tried googling for the answer, but came up > empty. I'm not sure of the right text combo to get a hit. > > Thanks > > -----Original Message----- > From: Alberto Massari [mailto:[email protected]] > Sent: Tuesday, November 03, 2009 11:27 PM > To: [email protected] > Subject: Re: What is the difference between configuring Xerces 3.0.1 > with--enable-netaccessor-curl vs --enable-netaccessor-socket? > > If you use --enable-netaccessor-socket you will not be able to specify a > proxy, as the code that reads from the Internet is simply working with plain > TCP sockets. If you use --enable-netaccessor-curl Xerces will use the APIs > provided by libcurl, so if you use the same API to setup a global proxy, you > will be able to use it. > > Alberto > > Dantzler, DeWayne C wrote: >> >> Hello >> >> Problem: there is a proxy between Xerces and the outside World and I need >> Xerces to perform XML validation against a schema which includes online >> references to an external scheme (e.g<xs:import >> namespace="http://www.w3.org/myspace >> schemaLocation="http://www.w3.org/schema.xsd"/>. >> >> What is the difference between configuring Xerces with >> --enable-netaccessor-curl vs --enable-netaccessor-socket? Basically, how >> does this effect the socket behavior of Xerces and why would I choose one >> over the other? >> >> Thanks >> >> >
