[enhancement] accept manually provided Cloudflare cookie

[JeffCarpenter]

I ran into an error trying to use Demonoid because the client doesn't answer a Cloudflare captcha challenge in issue #7637 .

I propose a feature that accepts a cookie manually captured from the user in order to answer said captcha.

[JeffCarpenter]

Thoughts? @cadatoiva

[garfield69]

Possible complications:

• Users that have Jackett running on seedboxes or headless servers, or remote (rather than local) systems.
• Non Dashboard users, i.e. apps such as Sonarr, Radarr, Ducketv that use torznab query via Jackett to fetch torrents/magnets.

[JeffCarpenter]

Possible complications:

* Users that have Jackett running on seedboxes or headless servers, or remote (rather than local) systems.

* Non Dashboard users, i.e. apps such as Sonarr, Radarr, Ducketv that use torznab query via Jackett to fetch torrents/magnets.

I do think the interactive/Selenium feature I suggested in the other issue was a stretch.

However what I'm proposing here is something more similar to the way it's done in the GazelleTracker or XSpeeds indexers.

cf #7187

[cadatoiva]

I can look into it, but I'm not sure this will work anyway. Couple of questions:

• Does CloudFlare stop presenting a ReCaptcha after you've successfully completed one on a normal home connection?
• Does it stop presenting ReCaptchas even if you're on a "blacklisted" IP (via VPN/Proxy/VPS block)?
• Is a cookie even how CloudFlare detects successful completion of a ReCaptcha, or do they possibly use some other method?
• Is the cookie specific to a single tracker's domain, or is it "global" by being attached to CloudFlare's domain?

I'll probably have more, but this is from the top of my head just knowing what I already do about ReCaptcha and CloudFlare.

[ngosang]

Take a look => #7643

[ngosang]

Another option could be to add and advanced option in the Web UI so you can configure the cookie in all trackers. This requires several changes in the code base but it could be the definitive solution to this kind of problems. This should be done at application level, not per tracker.
In a normal situation the user will configure none or user+pass or apikey depending on the tracker. But if it's not working he can always use the cookie.