0.46.2 — Cloudflare clearance reuse
Cloudflare clearance reuse (faster orzgk scraping)
The orzgk solver client now reuses the Cloudflare cf_clearance cookie across requests instead of re-solving the challenge on every call.
- The first request to a host solves via the configured solver (FlareSolverr / Byparr) and harvests
cf_clearance+ the solver's exact User-Agent. - Subsequent requests to the same host replay them on a plain direct GET (no browser) — falling back to the solver only if Cloudflare challenges again (cookie expired / rotated), so it's never worse than before.
- A burst to one host (wishlist pagination, the price cron) now costs one solve plus cheap replays instead of one ~30s solve each. A per-host lock collapses concurrent cache-misses into a single solve.
Works with every drop-in — notably Byparr, which (unlike FlareSolverr) has no server-side sessions, so the reuse is done client-side. No config or API changes.
Verified live (Byparr + orzgk): first request solved in ~24s, the next replayed in ~10s with the solver seeing exactly one challenge solve.
🐳 ghcr.io/dim145/figurecollector-{server,client,docs}:0.46.2
📝 Full changelog: 0.46.1...0.46.2