[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated NUTCH-1941:
----------------------------------------
Fix Version/s: (was: 2.4)
2.3.1
> 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
> Affects Versions: 2.3, 1.9
> Reporter: Lewis John McGibbney
> Assignee: Sebastian Nagel
> Priority: Trivial
> Fix For: 1.10, 2.3.1
>
> Attachments: NUTCH-1941-2x-v6.patch, NUTCH-1941-ITR2.patch,
> NUTCH-1941-itr3.patch, NUTCH-1941-itr4.patch, NUTCH-1941-v5.patch,
> NUTCH-1941-ver1.patch, NUTCH-1941-ver6.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)
