Thanks for dropping this on Remi.

For future reference you might want to check out this online book on
subversion [1]. Here at Nutch we use subversion for SCM and therefore this
is the program we use to create patches, applying them and hopefully
improving Nutch in the process ;0) It's straight forward no nonsense source
code management and is real easy to get to grips with given a little time.

Regarding this issue, unfortunately it has been open for a while and
additionally it doesn't look like there is quite enough of a requirement
from those using it to get a new implementation written up yet... I'm not
even using it at all...

Thanks again

Lewis

[1] http://svnbook.red-bean.com/en/1.7/index.html

On Thu, Jan 19, 2012 at 6:56 AM, Remi Tassing (Commented) (JIRA) <
j...@apache.org> wrote:

>
>    [
> https://issues.apache.org/jira/browse/NUTCH-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188961#comment-13188961]
>
> Remi Tassing commented on NUTCH-1086:
> -------------------------------------
>
> For the NTLMv2 issue I used a dirty solution in HttpResponse.java. Inside
> the creator and after the getResponseBodyAsStream()attempt:
> 1. I check the result code, if it's 500 (inside finally{...})
> 2. I use HttpUrlConnection to authenticate and open a connection
> 3. Then read the InputStream, get the Content and change the code to 200
>
> The problems with that solution are that:
> 1. The authentication keys are hardcoded
> 2. It doesn't check if the content is valid or not but set the return code
> to 200
> 3. Error code 500 doesn't necessarily mean that it's a NTLMv2
> authentication problem
>
> I have no idea on how to write patches to the "trunk"...
>
> Remi
>
> > Rewrite protocol-httpclient
> > ---------------------------
> >
> >                 Key: NUTCH-1086
> >                 URL: https://issues.apache.org/jira/browse/NUTCH-1086
> >             Project: Nutch
> >          Issue Type: Improvement
> >          Components: fetcher
> >            Reporter: Markus Jelsma
> >
> > There are several issues about protocol-httpclient and several comments
> about rewriting the plugin with the new http client libraries. There is,
> however, not yet an issue for rewriting/reimplementing protocol-httpclient.
> > http://hc.apache.org/httpcomponents-client-ga/
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>


-- 
*Lewis*

Reply via email to