Thanks Scott,
I'll check again. Some of the machinations that the other user has to
go through to get to the program may change his library list. I'll
check for other versions of HTTPAPI in *ALL libraries.
--J. Saunders
On Tue, Feb 28, 2012 at 1:54 PM, Scott Klement <[1]sk@xxxxxxxxxxxxxxxx>
wrote:
To the best of my knowledge, it's impossible to receive this message
unless you compiled without XML support.
If you answer "Build with XML support = Y" it doesn't even compile
the
module that contains the "not built with XML support" message. so I
don't see how this could possibly be a security issue. Either the
code
was compiled with XML or it wasn't.
More likely, there's more than one copy of HTTPAPI on the system,
and
when you sign in under another profile, you may be picking up a
different copy of HTTPAPI from a different library.
On 2/28/2012 1:26 AM, Jamey Saunders wrote:
> I have looked for this error and everything I've found stated that it
> was a result of HTTPAPI not being built with Expat support. The
> problem is that I did build it with Expat support, and all the
> webservice calls work running under my test profile. Using a
different
> profile, which has more authority than my test profile, and calling
the
> same program, I get the "HTTPAPI was not built with XML support"
error.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[2]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. mailto:sk@xxxxxxxxxxxxxxxx
2. http://www.scottklement.com/mailman/listinfo/ftpapi
----------------------------------------------------------------------- This is the FTPAPI mailing list. To unsubscribe, please go to: http://www.scottklement.com/mailman/listinfo/ftpapi -----------------------------------------------------------------------