nutch-dev mailing list archives

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

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

Claudio Martella commented on NUTCH-958:
----------------------------------------

that is the problem. right now the system does not allow the default scheme to be used as
a fallback, which is the reason i wrote this patch. that comes because of a bug in httpclient.

So, in order to have some control over the kind of authentication is used, which is the expected
behavior you also describe, the only way is through this workaround.

> 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