The documentation says: > If you omit the authMethod parameter (or pass 0), you let the program choose > the appropriate method to use. In this case, 4D sends an additional request > in order to negotiate the authentication method.
Are you omitting the authMethod parameter? If so, I suspect the error is happening in the "additional request". If you provide that, then HTTP Get should return the right HTTP error code. Hopefully you know ahead of time what method to use and this is better because you omit the extra request and should get any error code directly from the site. John DeSoi, Ph.D. > On Sep 27, 2019, at 11:07 AM, Paul Lovejoy via 4D_Tech <[email protected]> > wrote: > > I’m using HTTP AUTHENTICATE to authenticate connections to a web server. The > call to authenticate is immediately followed by a HTTP get(). The HTTP get > occasionally fails and I’ve been able to trace this to a failed HTTP > AUTHENTICATE, which appears to be an error from the website. However, it > appears there’s no way to know the authentification succeeded or failed. > There is no return code and OK doesn’t get set either. So I get various > errors such as -9935 from the subsequent call to HTTP get(), which isn’t very > helpful. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
