[ http://issues.apache.org/jira/browse/HTTPCLIENT-586?page=all ]
Anton Passiouk updated HTTPCLIENT-586:
--------------------------------------
Attachment: snippet.zip
snippet2.zip contains both test applets (Applet3: uses custom scheme, Applet4:
uses Jakarta's scheme)
> HttpClient v3: NTLM + SSL problem
> ---------------------------------
>
> Key: HTTPCLIENT-586
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-586
> Project: Jakarta HttpClient
> Type: Bug
> Versions: 3.0.1
> Environment: 1.4.2 Java plugin with MS IE 6
> Reporter: Anton Passiouk
> Attachments: logs_https_ntlm.zip, ntlm+https.log,
> ntlm_scheme_jakarta_vs_custom.zip, snippet.zip, snippet.zip
>
> Our application is a simple applet that tries to retrieve URLs contents from
> a web site.
> It detects browser's proxy parameters and uses the Jakarta HttpClient to
> request the needed URL.
> First we had problems to simply authenticate ourselves with NTLM so we
> slightly changed the implementation of the NTLM protocol to hash the password
> differently (you will find it in the snippet attached to this bug).
> But now we can't get the application working with this proxy when the target
> web site is secured (HTTPS, no authentication). And it works just fine with
> another proxy using "Basic" auth scheme (regardless if the site is in HTTP
> and HTTPS).
> To summarize:
> Basic proxy:
> HTTP: OK
> HTTPS: OK
> NTLM proxy:
> HTTP: OK
> HTTPS: NOK -> logs are attached
> The exact proxy version is: Microsoft ISA 2000 3.0.1200.365 SP2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
