These are chat archives for IndySockets/Indy
EIdHTTPProtocolException, and enabling
hoNoProtocolErrorExceptionand then checking the
ResponseCodemanually. The end result is the same.
TIdSSPINTLMAuthenticationsucceeds (SSPI uses credentials stored in the calling thread, and the OS handles the actual authentication data) whereas
TIdNTLMAuthenticationfails (it requires username/password, and performs authentication manually). Just adding the IdAuthentication units to your
usesclause to register the classes does not guarantee success, you still have to make sure things are setup correctly in
TIdHTTP. There is just not enough information to go on to diagnose what the actual problem is. You are going to have to debug it further.