FlareSolverr Support #2081
Labels
effort/high
Requires 3 or more days
enhancement
New feature or request
gain/low
Affects few people or adds marginal value
Checklist
Description
Several years ago, a solution like cloudscraper may have been ideal. Now, there doesn't seem to be any actively maintained solution outside of FlareSolverr. This solution wouldn't be a good build-in, but it can function as a proxy with a couple adjustments.
I was able to put together a somewhat viable proof of concept in #2079 (would be re-engineered if desired, though).
The caveat is that FlareSolverr doesn't seem to properly pass along return codes right now. That would mean it can only be reliably used for message and possibly for redirect_url. When FlareSolverr is detected, we would have status_code requests bypass the proxy and function normally.
Seems that some messages may need a minor tweak depending on how sites handle l10n and such, but they would be similar if changed at all (as in the data.json diff).
Would this partial support be desired, or would we prefer to wait until FlareSolverr more properly supports status_code as well?
The text was updated successfully, but these errors were encountered: