Using a HTTP tracing tool where you could see all of the request/response values with headers might provide useful clues. My other idea would be to drop HTTP AUTHENTICATE and just build the authentication digest headers yourself.
John DeSoi, Ph.D. > On Sep 27, 2019, at 12:47 PM, Paul Lovejoy <paul.e.love...@gmail.com> wrote: > > Thanks for your feedback. I’m passing “2” in the extra parameter. The > following HTTP get() is returning an error -9935, badly formed XML. The HTTP > get is supposed to be retrieving XML, actually. So the error is not totally > off base. But I would prefer to know that authentification failed, not the > HTTP get() ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
