What causes "[%s] %s触发 Cloudflare Managed Challenge (HTTP %d)" in fish2018/pansou?

Back off and retry much later; managed challenges usually cannot be bypassed programmatically.

fish2018/pansou · error

[ ] 触发 Cloudflare Managed Challenge (HTTP )

Error message

[%s] %s触发 Cloudflare Managed Challenge (HTTP %d)

What it means

httpStatusError inspects the cf-mitigated response header; when it equals "challenge" the request was intercepted by a Cloudflare Managed Challenge rather than an ordinary HTTP failure, and this dedicated error is returned naming the action (e.g. 搜索 or detail fetch) and status code. It tells the caller the site's bot protection actively challenged this request.

Solutions

Back off and retry much later; managed challenges usually cannot be bypassed programmatically.
Update cloudscraper or its browser-emulation profile to a newer fingerprint.
Reduce request rate and add randomized delays to avoid tripping bot detection.
Route through residential proxies or a headless-browser solver service.

Example fix

// before
if err != nil { return err }
// after
if err != nil {
    var cfErr *CloudflareChallengeError
    if errors.As(err, &cfErr) {
        time.Sleep(10 * time.Minute) // cool down before next attempt
    }
    return err
}

Defensive patterns

Strategy: fallback

Try / catch

if err != nil {
    if strings.Contains(err.Error(), "Managed Challenge") {
        return p.fallbackSource(keyword) // alternate mirror or cache
    }
    return err
}

Prevention

Throttle request rate with randomized delays to avoid triggering challenges.
Keep cloudscraper and its browser fingerprint current.
Prefer residential IPs over datacenter ranges.
Implement a fallback data source or cached results for challenged periods.

When it happens

Trigger: Any request through getPage/fetchDetailPageLinks that receives a response with header cf-mitigated: challenge — executeSearch on the search page or fetchDetailPageLinks on a detail page. Callers wrap this into 搜索请求失败? no: executeSearch calls it directly on non-200 status.

Common situations: Cloudflare tightened protection for the site; the scraper's fingerprint is stale/detected; scraping from datacenter IPs; too-high request rate triggering managed challenge enforcement.

Related errors

AI-assisted analysis of fish2018/pansou@beaa561337 (2026-09-07). Data as JSON: /api/errors/d46cc1e5b3531b7d. Report an issue: GitHub.

Appendix: source

Thrown at plugin/diduan/diduan.go:196

	// 解析HTML提取搜索结果
	doc, err := goquery.NewDocumentFromReader(resp.Body)
	if err != nil {
		return nil, fmt.Errorf("[%s] 解析搜索结果HTML失败: %w", p.Name(), err)
	}

	return p.parseSearchResults(doc)
}

// getPage 串行化 cloudscraper 调用，避免其 stealth 计数器并发竞争。
func (p *DiduanPlugin) getPage(rawURL string) (*http.Response, error) {
	p.scraperMu.Lock()
	defer p.scraperMu.Unlock()
	return p.scraper.Get(rawURL)
}

func (p *DiduanPlugin) httpStatusError(action string, resp *http.Response) error {
	if strings.EqualFold(resp.Header.Get("cf-mitigated"), "challenge") {
		return fmt.Errorf("[%s] %s触发 Cloudflare Managed Challenge (HTTP %d)", p.Name(), action, resp.StatusCode)
	}
	return fmt.Errorf("[%s] %sHTTP状态错误: %d", p.Name(), action, resp.StatusCode)
}

// parseSearchResults 解析搜索结果HTML
func (p *DiduanPlugin) parseSearchResults(doc *goquery.Document) ([]model.SearchResult, error) {
	var results []model.SearchResult

	// ddys.io 当前页面使用 movie-card；影视搜索区的第一个 h2 下才是搜索结果，
	// 后面的 movie-card 是推荐内容，不能一并请求详情页。
	var cards *goquery.Selection
	doc.Find("h2").EachWithBreak(func(_ int, heading *goquery.Selection) bool {
		if strings.HasPrefix(strings.TrimSpace(heading.Text()), "影视") {
			cards = heading.Parent().Parent().Find(".movie-card")
			return false
		}
		return true
	})

View on GitHub (pinned to beaa561337)