Backup_Repos/Prowlarr
1
0
Fork 0
mirror of https://github.com/Prowlarr/Prowlarr synced 2026-05-07 04:00:32 +02:00
Code Issues Projects Releases Wiki Activity

Update code comment to reflect actual root cause

Browse source 
The cf_clearance cookie is not bound to TLS fingerprint — testing
confirmed it works from curl (different TLS stack). The real issue is
that CF selectively challenges by IP/UA, so FlareSolverr may not
receive a challenge and returns no cf_clearance cookie.
This commit is contained in:
Etheirystech 2026-04-09 09:16:01 +02:00
parent 65905566dd
commit 714d7980b4
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
src/NzbDrone.Core/IndexerProxies/FlareSolverr/FlareSolverr.cs
View file

@ -72,10 +72,9 @@ public override HttpResponse PostResponse(HttpResponse response)
InjectCookies(newRequest, result);
// Use FlareSolverr's response body directly when available.
// A second HTTP request with the extracted cookies would get rejected
// because cf_clearance is validated against the TLS fingerprint of the
// client that solved the challenge (FlareSolverr's headless browser),
// which differs from .NET HttpClient's fingerprint.
// When CF selectively challenges by IP/UA, FlareSolverr may not
// receive a challenge and thus returns no cf_clearance cookie.
// A second request without that cookie gets 403'd.
if (result.Solution.Response.IsNotNullOrWhiteSpace())
{
var headers = new HttpHeader();