wodHttpDLX ActiveX Control - ProxyAuthentication Property
      
 

Description

Determines type of authentication with the proxy server.


Property type

A HttpAuthentications enumeration.  


Syntax

object.ProxyAuthentication [= value]



The ProxyAuthentication Property syntax has these parts:

Part Description
object An expression evaluating to an object of type wodHttpDLX.
value A HttpAuthentications enumeration, as described in settings.

Settings

The settings for value are:

Constant Value Description
 AuthNone 0 No authentication
 AuthAutomatic 1 Auto select authentication
 AuthBasic 2 Basic authentication
 AuthNTLM 3 NTLM authentication
 AuthDigest 4 Digest authentication

Remarks

ProxyAuthentication property determines mode of authentication for wodHttpDLX when using proxy server ProxyWEBStandard type.

For this purpose, wodHttpDLX can authenticate using Basic and NTLM authentication. NTLM is far more secure, because password is *never* sent over insecure network to the remote side. Rather, sequence of challenge/response messages are sent during this authentication. wodHttpDLX has been tested with MS Proxy  and IIS server for NTLM authentication. Basic authentication (using base64 encoded login and password) if far more widespread, and is used by many proxy and WEB servers.

If you don't want to authenticate with the proxy, you can either set ProxyAuthentication to AuthNone value, or you can leave ProxyLogin/ ProxyPassword properties empty.

If you specify authentication mode explicitly, using AuthBasic or AuthNTLM value, wodHttpDLX will immediately in your next request send authentication request to the proxy server.

The best option (and default, of course) is AuthAutomatic value, which will try to access the resource without any login/password information, and then resend requests WITH authentication information only if server returned 'access denied' response. In this case, wodHttpDLX can issue many requests in order to pass through proxy and WEB server protections. Make sure that AutoRedirect property is set to True (it is by default) in such cases. After all those requests are internally sent, Done event will be fired only once - when wodHttpDLX has completed it's job, either successfully or with error response from the remote side.