nutch-dev mailing list archives

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

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

Markus Jelsma commented on NUTCH-958:
-------------------------------------

Hi Claudio. Is this desired behaviour? Shouldn't the default be used as fallback if the negotiated
schema fails instead forcing default as only scheme?

> 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