The purpose of TIdAuthenticationManager
is to keep a cache of authentication parameters are used to successfully log in to particular URLs. Nothing more. TIdHTTP
does not make use of that cache during authentication, but you can utilize it yourself in the OnSelectAuthentication
and OnAuthentication
events, if desired.
Which authentication scheme is actually being used in this situation? Which header(s) is the webdav module expecting the character encoding to be specified in? In Indy 10, the NTLM classes support Unicode strings during hashing, but they use UTF-16, not UTF-8.
Can the webdav author provide more info about what he is actually expecting from you?
To answer your other questions:
(1) What 'logintype' are you referring to? There is no such property or parameter in Indy.
(2) hoForceEncodeParams only applies when calling Post() to send a TStrings object for 'application/x-www-form-urlencoded' requests. It has no effect on authentication.
(3) To see what data is being transmitted back and forth over the connection, you can attach a TIdLog...
component, such as TIdLogFile
or TIdLogEvent
, to the Intercept
property. Or else use an external packet sniffer, such as Wireshark.