[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364270#comment-14364270
]
Asitang Mishra commented on NUTCH-1941:
---------------------------------------
Hi,
-clutter of classpath: I used eclipse to create a patch.
-strange logging: just was giving some strange outputs so that I could find the
changes in the Log files.
-unknown files/classes: I was working on nutch 1x and not 2x for this issue.
-"no actual implementation which would all us to define a list of agent names
from which to rotate." : because I was using a counter for that.
I will make the required changes and attach a new patch. If I start looking in
nutch 2x for this, it may take a little longer.
Thank you for your comments.
> Optional rolling http.agent.name's
> ----------------------------------
>
> Key: NUTCH-1941
> URL: https://issues.apache.org/jira/browse/NUTCH-1941
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher, protocol
> Reporter: Lewis John McGibbney
> Priority: Trivial
> Attachments: nutch.patch
>
>
> In some scenarios, even whilst adhering to fetcher.crawl.delay, web admins
> can block your fetcher based merely on your crawler name.
> I propose the ability to implement rolling http.agent.name's which could be
> substituted every 5 seconds for example. This would mean that successive
> requests to the same domain would be sent with different http.agent.name.
> This behavior should be off by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
