nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Nioche (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NUTCH-958) Httpclient scheme priority order fix
Date Fri, 18 Mar 2011 16:44:29 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008508#comment-13008508
] 

Julien Nioche commented on NUTCH-958:
-------------------------------------

I had a look at upgrading to a more recent version of httpclient but it was a substantial
job as most of the API had changed. We'll definitely do that for Nutch 2.0 at some point.

What about marking this issue as won't fix and move it out of 1.3? As you said people will
find your patch here if they have the same problem and can easily apply it. 

> 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

Mime
View raw message