gocolly/colly

cache and proxy

Open

#187 创建于 2018年7月10日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)Go (24,898 star) (1,837 fork)batch import
enhancementhelp wanted

描述

Hey guys,

I have an issue. In real world of scrappers when using proxies, checking if You have response code 200 or 500 is simply not enough. Plenty of proxies or even website itself can throw an output with code 200 which is invalid from developer point of view and yet its getting cached. Is there any way to apply some kind of custom logic which would determine if response is what we want? For example:

colly.CacheDir("some/dir", func(resp) {
   if bytes.Contains(resp.Body, []byte("some magic marker")) {
      return false // don't cache
   }
})

I'm new to colly and i was digging thru source code for a bit, but didn't find such of feature. It's also useful without proxies.

贡献者指南

技术栈
go
领域
backendtooling
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go basicscolly framework understanding
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
The user proposes adding a custom validation function to Colly's caching mechanism. To implement, examine the existing CacheDir function in the colly source (likely in colly.go or cache.go). The callback should allow users to inspect the response and decide whether to cache it. A pull request introducing an optional validation callback parameter to CacheDir would be appropriate. Review any existing discussions in the issue comments for additional context.