You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- FlareSolverr version:3.3.17
- Last working FlareSolverr version:Unk- Operating system:All
Description
Status codes are not directly supported by Selenium and therefore FlareSolverr always returns 200.
Response headers are not directly supported by Selenium and therefore FlareSolverr always returns empty headers.
challenge_res.status=200# todo: fix, selenium not provides this infochallenge_res.headers= {} # todo: fix, selenium not provides this info
I don't believe this is documented anywhere outside of the code, so new users may encounter issues while debugging. This should serve as an easily searchable Issue to save their sanity and hours of debugging until this is resolved.
The text was updated successfully, but these errors were encountered:
My personal goal was (& is when free) to shoehorn support into flaresolverr by interacting with the browser behind selenium directly, rather than interacting with selenium (since they don't want to support it, as linked)
While Selenium doesn't support those items directly, the devtools for whichever browser are still somewhat exposed, giving us a theoretical side channel, even if it's not pretty
It's a low priority right now but something I'd like to poke at eventually
Environment
Description
Status codes are not directly supported by Selenium and therefore FlareSolverr always returns 200.
Response headers are not directly supported by Selenium and therefore FlareSolverr always returns empty headers.
From flaresolverr_service.py:
I don't believe this is documented anywhere outside of the code, so new users may encounter issues while debugging. This should serve as an easily searchable Issue to save their sanity and hours of debugging until this is resolved.
The text was updated successfully, but these errors were encountered: