[
https://issues.apache.org/jira/browse/NUTCH-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381871#comment-14381871
]
Lewis John McGibbney commented on NUTCH-1941:
---------------------------------------------
I am completely with [~wastl-nagel] on this one. I've refrained from engaging
in too much conversation (although I have had a fair amount of convo with
[~asitang] offline) mainly because the conversation got overly complex IMHO
very quickly and I wanted to see that exchange of ideas finish without me
butting in. I really feel that keeping this simple it best. That was my initial
intent. This based with [~markus17]'s initial concerns mean that keeping it
simple and off by default were my priority for this task.
[~asitang], thank you so much for acknowledging the various feedback. If you
are able to provide a patch to accommodate solution 2 that would be ideal, if
not then I can jump on board here.
> 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-itr3.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)
