achmad 452918ac82 fix: detect Cloudflare challenge on HTTP 200 responses ...

Some anti-bot challenge pages return HTTP 200 instead of 403/503,
bypassing the FS fallback. Read response body on 200, check for
challenge indicators, and fall through to FlareSolverr if detected.

2026-05-14 23:19:31 +07:00

..

flare

feat(sourcetest): add -v flag with verbose manga list output

2026-05-14 13:23:29 +07:00

client.go

fix: detect Cloudflare challenge on HTTP 200 responses

2026-05-14 23:19:31 +07:00

flaresolverr.go

feat: replace net/http with httpcloak for Chrome TLS fingerprint

2026-05-14 22:31:09 +07:00

graphql.go

change perms

2026-05-11 06:48:23 +00:00

headers.go

change perms

2026-05-11 06:48:23 +00:00