You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Doğacan Güney (JIRA)" <ji...@apache.org> on 2007/04/24 16:10:15 UTC
[jira] Created: (NUTCH-474) Fetcher2 sets server-delay and blocking
checks incorrectly
Fetcher2 sets server-delay and blocking checks incorrectly
----------------------------------------------------------
Key: NUTCH-474
URL: https://issues.apache.org/jira/browse/NUTCH-474
Project: Nutch
Issue Type: Bug
Components: fetcher
Affects Versions: 1.0.0
Reporter: Doğacan Güney
Fix For: 1.0.0
1) Fetcher2 sets server delay incorrectly. It sets the delay to minCrawlDelay if maxThreads == 1 and to crawlDelay otherwise. Correct behaviour should be the opposite.
2) Fetcher2 sets wrong configuration options so host blocking is still handled by the lib-http plugin (Fetcher2 is designed to handle blocking internally).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (NUTCH-474) Fetcher2 sets server-delay and blocking checks incorrectly
Posted by Doğacan Güney <do...@gmail.com>.
On 6/28/07, Hudson (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/NUTCH-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508747 ]
>
> Hudson commented on NUTCH-474:
> ------------------------------
>
> Integrated in Nutch-Nightly #131 (See [http://lucene.zones.apache.org:8080/hudson/job/Nutch-Nightly/131/])
*sigh*
I wrote NUTCH-474 instead of NUTCH-434 in svn log. Sorry everyone...
>
> > Fetcher2 sets server-delay and blocking checks incorrectly
> > ----------------------------------------------------------
> >
> > Key: NUTCH-474
> > URL: https://issues.apache.org/jira/browse/NUTCH-474
> > Project: Nutch
> > Issue Type: Bug
> > Components: fetcher
> > Affects Versions: 1.0.0
> > Reporter: Doğacan Güney
> > Assignee: Andrzej Bialecki
> > Fix For: 1.0.0
> >
> > Attachments: fetcher2.patch
> >
> >
> > 1) Fetcher2 sets server delay incorrectly. It sets the delay to minCrawlDelay if maxThreads == 1 and to crawlDelay otherwise. Correct behaviour should be the opposite.
> > 2) Fetcher2 sets wrong configuration options so host blocking is still handled by the lib-http plugin (Fetcher2 is designed to handle blocking internally).
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
Doğacan Güney
[jira] Closed: (NUTCH-474) Fetcher2 sets server-delay and blocking
checks incorrectly
Posted by "Andrzej Bialecki (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki closed NUTCH-474.
-----------------------------------
Resolution: Fixed
Assignee: Andrzej Bialecki
Fixed in rev. 532088. Thanks!
> Fetcher2 sets server-delay and blocking checks incorrectly
> ----------------------------------------------------------
>
> Key: NUTCH-474
> URL: https://issues.apache.org/jira/browse/NUTCH-474
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Reporter: Doğacan Güney
> Assigned To: Andrzej Bialecki
> Fix For: 1.0.0
>
> Attachments: fetcher2.patch
>
>
> 1) Fetcher2 sets server delay incorrectly. It sets the delay to minCrawlDelay if maxThreads == 1 and to crawlDelay otherwise. Correct behaviour should be the opposite.
> 2) Fetcher2 sets wrong configuration options so host blocking is still handled by the lib-http plugin (Fetcher2 is designed to handle blocking internally).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (NUTCH-474) Fetcher2 sets server-delay and
blocking checks incorrectly
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508747 ]
Hudson commented on NUTCH-474:
------------------------------
Integrated in Nutch-Nightly #131 (See [http://lucene.zones.apache.org:8080/hudson/job/Nutch-Nightly/131/])
> Fetcher2 sets server-delay and blocking checks incorrectly
> ----------------------------------------------------------
>
> Key: NUTCH-474
> URL: https://issues.apache.org/jira/browse/NUTCH-474
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Reporter: Doğacan Güney
> Assignee: Andrzej Bialecki
> Fix For: 1.0.0
>
> Attachments: fetcher2.patch
>
>
> 1) Fetcher2 sets server delay incorrectly. It sets the delay to minCrawlDelay if maxThreads == 1 and to crawlDelay otherwise. Correct behaviour should be the opposite.
> 2) Fetcher2 sets wrong configuration options so host blocking is still handled by the lib-http plugin (Fetcher2 is designed to handle blocking internally).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (NUTCH-474) Fetcher2 sets server-delay and blocking
checks incorrectly
Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NUTCH-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doğacan Güney updated NUTCH-474:
--------------------------------
Attachment: fetcher2.patch
> Fetcher2 sets server-delay and blocking checks incorrectly
> ----------------------------------------------------------
>
> Key: NUTCH-474
> URL: https://issues.apache.org/jira/browse/NUTCH-474
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Reporter: Doğacan Güney
> Fix For: 1.0.0
>
> Attachments: fetcher2.patch
>
>
> 1) Fetcher2 sets server delay incorrectly. It sets the delay to minCrawlDelay if maxThreads == 1 and to crawlDelay otherwise. Correct behaviour should be the opposite.
> 2) Fetcher2 sets wrong configuration options so host blocking is still handled by the lib-http plugin (Fetcher2 is designed to handle blocking internally).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.