[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364120#comment-14364120
]
Asitang Mishra edited comment on NUTCH-1941 at 3/16/15 10:45 PM:
-----------------------------------------------------------------
I tried to rotate the name of the agent in the httpResponse class (package
org.apache.nutch.protocol.http)
Used a static counter initialized in the httpBase class. With each new request
to a url, the name of the bot will be changed.
Added nutch.patch
was (Author: asitang):
I tried to rotate the name of the agent in the httpResponse class (package
org.apache.nutch.protocol.http)
Used a static counter initialized in the httpBase class. With each new request
to a url, the name of the bot will be changed.
> Optional rolling http.agent.name's
> ----------------------------------
>
> Key: NUTCH-1941
> URL: https://issues.apache.org/jira/browse/NUTCH-1941
> Project: Nutch
> Issue Type: Bug
> 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)
