Article View: borland.public.cppbuilder.internet.socket
Article #452Re: TIdHTTP and Windows Authentication
From: Remy Lebeau (TeamB)
Date: Wed, 13 Feb 2008 23:22
Date: Wed, 13 Feb 2008 23:22
28 lines
2629 bytes
2629 bytes
"Aladin J." <j_aladin@hotmail.com> wrote in message news:47b3658e@newsgroups.borland.com... > WWW-Authenticate: Negotiate > WWW-Authenticate: NTLM The server is asking for "Negotiate" first. You have to use TIdSSPINTLMAuthentication instead of TIdNTLMAuthentication for that. However, since the server is also stating that "NTLM" is supported, then TIdNTLMAuthentication should have worked ok. Something else has to be happening. Since TIdNTLMAuthentication's constructor loads the OpenSSL DLLs, you probably don't have the right version installed. That is the only thing I can think of that would cause the constructor to throw an exception. > I supprise in request caused by it should have more tag liked > "Authorization: NTLM TlRMTVNTUAA..........." but it's gone. TIdHTTP does not send authorization credentials unless the server explicitally asks for them first. In this case, you sent a request, and the server replied asking for the credentials. There should have been a second request sent automatically after that which included the credentials that TIdNTLMAuthentication generates. Of course, if you can't create the TIdNTLMAuthentication object to begin with, then it won't be available to generate that data. Gambit
Technical Details
Message-ID:
<47b37b92$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<47ab27fc@newsgroups.borland.com> <47ab4352$1@newsgroups.borland.com> <47abc8cd@newsgroups.borland.com> <47b08ae4$1@newsgroups.borland.com> <47b19477@newsgroups.borland.com> <47b1d8a6$1@newsgroups.borland.com> <47b2604f@newsgroups.borland.com> <47b27339$1@newsgroups.borland.com> <47b28f19@newsgroups.borland.com> <47b29d49$1@newsgroups.borland.com> <47b2f1f8$1@newsgroups.borland.com> <47b32b3f$2@newsgroups.borland.com> <47b3658e@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,ecad3022b25c513d X-Google-Attributes: gid11508e,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <47ab27fc@newsgroups.borland.com> <47ab4352$1@newsgroups.borland.com> <47abc8cd@newsgroups.borland.com> <47b08ae4$1@newsgroups.borland.com> <47b19477@newsgroups.borland.com> <47b1d8a6$1@newsgroups.borland.com> <47b2604f@newsgroups.borland.com> <47b27339$1@newsgroups.borland.com> <47b28f19@newsgroups.borland.com> <47b29d49$1@newsgroups.borland.com> <47b2f1f8$1@newsgroups.borland.com> <47b32b3f$2@newsgroups.borland.com> <47b3658e@newsgroups.borland.com> Subject: Re: TIdHTTP and Windows Authentication Date: Wed, 13 Feb 2008 15:22:27 -0800 Lines: 30 Organization: Lebeau Software X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 207.178.157.90 Message-ID: <47b37b92$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1202944914 207.178.157.90 (13 Feb 2008 15:21:54 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail