Darcy McNally wrote: > Arno, > Thanks very much for the prompt reply. One further question. When > setting HttpCli for NTLM is it also necessary to set/pass the > username and password, as would be done for a proxy server setup e.g. > HttpCli->ProxyUsername & HttpCli->ProxyPassword.
If the server behind the proxy requires authentication set properties Username, Password and ServerAuth. If the proxy requires authentication set properties ProxyUsername, ProxyPassword and ProxyAuth. Both proxy and server might support multiple authentication types. Event BeforeAuth (ICSv7) triggers for each type they support. Note that NTLM and Digest require persistent connections to work, forgot to mention that yesterday. That means properties ProxyConnection and/or Connection should be set to "keep-alive" at least with HTTP v1.0. > > As I'm unable to mimic an NTLM network from my workplace I need to, > reluctantly, ask one of our our customers to test for us. This is the > reason I am getting as much info as possible on the HttpCli NTLM > parameters/setup. Server authentication can be tested against the OverbyteIcsWebServ demo (Delphi). There are free NTLM proxies downloadable from the internet. A member of this list suggested this one: 3proxy (http://3proxy.ru/board/?l=EN) Console app with manually edited conf files, but in part of auth settings are quite simple -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
