Authentication property determines if wodHttpDLX should
authenticate with the web server to access protected
resource. In most cases this is not needed, but sometimes
access to restricted areas may be needed.
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 server,
you can either set Authentication to AuthNone value, or you can leave login/password
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
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
Don't forget that AuthNTLM may use
MyHostname
property to identify your computer to the server! You may want to clear it out if you're accessing HTTP server outside your
domain!
When AuthWindowsIntegrated is selected, wodHttpDLX will send
login and password of currently logged in Windows user. This type of
authentication is used with NTLM authentication type.