[ https://issues.apache.org/jira/browse/NUTCH-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008422#comment-13008422 ]
Markus Jelsma commented on NUTCH-958: ------------------------------------- Claudio, i am not sure if this workaround should be committed at all. If the devs agree then it should: - be patched for 2.0 as well - add a configuration option to enable your workaround so to prevent breaking other user's HTTP authentication methods > Httpclient scheme priority order fix > ------------------------------------ > > Key: NUTCH-958 > URL: https://issues.apache.org/jira/browse/NUTCH-958 > Project: Nutch > Issue Type: Bug > Components: fetcher > Affects Versions: 1.3 > Reporter: Claudio Martella > Fix For: 1.3 > > Attachments: httpclient.diff > > > Httpclient will try to authenticate in this order by default: ntlm, digest, > basic. > If you set as default a scheme that comes in this list after a scheme that is > negotiated by the server, and this authentication fails, the default scheme > will not be tried. > I.e. if you set digest as default scheme but the server negotiates ntlm, the > client will still try ntlm and fail. > The fix sets the default scheme as the only possible scheme for > authentication for the given realm by setting the authentication priorities > of httpclient. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira