[
https://issues.apache.org/jira/browse/HTTPCLIENT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922075#action_12922075
]
Oleg Kalnichevski commented on HTTPCLIENT-919:
----------------------------------------------
Karl
Given that we now have an explicit OK to include NTLM implementations in the
ASF code (LEGAL-80), I can commit your patch to the project repository.
However, there is one minor technicality that we need to discuss first.
HttpClient 3.1 is effectively EOL and is not planned to have any official
releases any more. So, the patch needs to be ported to the 4.x API. Would you
have time and inclination to work on the port or is that something I would have
to do myself?
Oleg
> NTLM implementation lacks support for NTLMv1, NTLMv2, and NTLM2 Session forms
> of NTLM
> -------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-919
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-919
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpAuth
> Reporter: Karl Wright
> Fix For: Future
>
> Attachments: ntlmv2-etc.patch
>
>
> The current HttpClient implementation lacks support for all enhancements to
> NTLM after Windows 95. That includes NTLMv1, NTLMv2, and NTLM2 Session
> Response varieties of the protocol.
> This seriously impacts the usability of HttpClient in enterprise situations,
> which has required the Lucene Connector Framework team to extend HttpClient
> to address the issue.
> I've attached a patch which contains the implementation used by LCF.
--
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: [email protected]
For additional commands, e-mail: [email protected]
