[ 
https://issues.apache.org/jira/browse/NUTCH-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Susam Pal updated NUTCH-559:
----------------------------

    Attachment: NUTCH-559v0.2.patch

Uploading a revised (v0.2) patch which accommodates most of the suggestions by 
Doğacan. A few points I want to discuss:-

* Extending the authentication to work for more than one host was in my mind 
but I found too many possible cases. So I was planning to have a different 
configuration file where all the authentication rules can be mentioned to 
override the corresponding 'conf/nutch-site.xml' properties. The different 
possible cases are:
** Different credentials for different domain or sub-domains, say, example.com, 
ad.example.com, example.net, etc.
** Different credentials for different hosts.
** Different credentials for different realms.
* I removed cookie related code earlier because I didn't find it to work (even 
before merging my work). However, I have brought them back in the revised 
patch. We can discuss more on this if required.
* I have restored most of the original response reading code except for 
'calculateTryToRead'. This method is not checking for 'Content-Length' limit. 
The content-length limit check present in this patch is similar to that of 
'protocol-http' which is simpler and correct.

If the idea of having a separate authentication configuration file looks good, 
I can work on it when I get some free time.

> NTLM, Basic and Digest Authentication schemes for web/proxy server
> ------------------------------------------------------------------
>
>                 Key: NUTCH-559
>                 URL: https://issues.apache.org/jira/browse/NUTCH-559
>             Project: Nutch
>          Issue Type: Improvement
>          Components: fetcher
>    Affects Versions: 1.0.0
>            Reporter: Susam Pal
>         Attachments: NUTCH-559v0.1.patch, NUTCH-559v0.2.patch
>
>
> Added basic, digest and NTLM authentication schemes to protocol-httpclient. 
> The authentication schemes can be configured for proxy server as well as web 
> servers of a domain. HTTP authentication can take place over HTTP/1.0, 
> HTTP/1.1 and HTTPS.
> The authentication guide can be found here: 
> [http://wiki.apache.org/nutch/HttpAuthenticationSchemes].

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to