[
https://issues.apache.org/jira/browse/HTTPCLIENT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837942#action_12837942
]
Karl Wright commented on HTTPCLIENT-919:
----------------------------------------
Reviewers here want to know if there's any controlling legal ASF document that
describes the described policy available for their perusal. A URL will do, or
even a document title (if you recall seeing such a thing anywhere).
Also, FWIW, our expert here believes that ASF's legal structure may protect
individual Apache contributors from liability concerns of this kind. "That's
kind of why Apache exists," was the comment.
> 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]
