[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364214#comment-14364214
]
Lewis John McGibbney commented on NUTCH-1941:
---------------------------------------------
I've looked at this patch quickly.
bq. Regarding the patch, i contains a lot of clutter about class paths which i
am unfamiliar with. It doesn't look like a trunk patch and i don't remeber 2x
having these files. Do we need them?
The patch does not contain anything AFAICT that relates to revolving user agent
names for a Nutch crawler.
Please ensure that you have included everything in your patch that you tried to
include please [~asitang], from what I can see, there is a bunch of strange
logging, a bunch of dummy files which are not required and finally no actual
implementation which would all us to define a list of agent names from which to
rotate.
[~markus17], there is no doubt that your comments are very valid. You ask a few
questions. I'll get back to you ASAP Markus. Thanks :)
> 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)
