[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721104#action_12721104
 ] 

Konstantin Kasatkin commented on HTTPCLIENT-579:
------------------------------------------------

Guys, I'd recommend you before sending your requests to figure out how 
src/build.xml really works.
It unpacks original commons-httpclient-3.0.jar, substitutes necessary classes 
and packs compilled ones into commons-httpclient-3.0-ntlm-2.0.jar.

Have you tried just to run build.xml, what's the problem?

> NTLMv2 support
> --------------
>
>                 Key: HTTPCLIENT-579
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-579
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpAuth
>    Affects Versions: 3.0 Final
>         Environment: WIndows 2000 Pro SP4, JDK 1.4.2
>            Reporter: Konstantin Kasatkin
>             Fix For: 3.1 Alpha 1
>
>         Attachments: ntlmv2-session-security.diff, NTLMv2.rar, NTLMV21.RAR
>
>
> Hello guys,
> recently I've encouner the problem how to interact with HTTP resourses 
> protected tough security policy allowed to use only NTLMv2 authorization 
> scheme from a java application.
> Earlier I used httpclient to accomplish NTLMv1 authorization, but when I was 
> requested to move to NTLMv2 I was surprised, that httpclient does not support 
> this.
> I've dug all the Internet and found some articles and examples how to 
> implement it, and finally having compiled all this enormous heap of 
> information, I have a couple modified classes from httpclient project, that 
> I'd like to share with you and other users of httpclient.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to