[
https://issues.apache.org/jira/browse/NUTCH-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008432#comment-13008432
]
Claudio Martella commented on NUTCH-958:
----------------------------------------
this workaround was necessary for my work and introduced an expected behavior.
I understand it's not clean, but the actual behavior of nutch isn't correct
either. Maybe it can be useful for somebody else and maybe it's enough to keep
it here so people can find it and apply the patch if they like, so that it
doesn't have to be commited.
The "right" way would probably just pass through moving to httpclient4.
> 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
