[
https://issues.apache.org/jira/browse/DROIDS-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935280#action_12935280
]
Florent ANDRE commented on DROIDS-105:
--------------------------------------
Thanks for pointing this.
Did you see a way to change the final status of contentLoader in HttpProtocol ?
You cachingContentLoader class can be use inside droids ? If yes can you
provide a patch from the project's root ? It's more expressive and
understandable that an attached class.
++
> missing caching for robots.txt
> ------------------------------
>
> Key: DROIDS-105
> URL: https://issues.apache.org/jira/browse/DROIDS-105
> Project: Droids
> Issue Type: Improvement
> Components: core
> Reporter: Paul Rogalinski
> Attachments: CachingContentLoader.java
>
>
> the current implementation of the HttpClient will not cache any requests to
> the robots.txt file. While using the CrawlingWorker this will result in 2
> requests to the robots.txt (HEAD + GET) per crawled URL. So when crawling 3
> URLs the target server would get 6 requests for the robots.txt.
> unfortunately the contentLoader is made final in HttpProtocol, so there is no
> possibility to replace it with a caching Protocol like that one you'll find
> in the attachment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
