[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376357#comment-14376357
]
Asitang Mishra commented on NUTCH-1941:
---------------------------------------
Hi @Sebastian Nagel, thanks for the comments. I will do the rework and post
again. Meanwhile could you please elaborate more on: "formatting (see []), Java
syntax (e.g., (word)!="\n")".
Also, The patch is still polite as it is up to the user to put the agent.txt,
if they don't then it will resume it's default behavior. But I will use a
property to set it (I was thinking the same thing to do, but then thought not
to touch the property side).
> 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-1941-ITR2.patch, NUTCH-1941-ver1.patch,
> agent.names.txt, 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)
