-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status code always 200 // Response headers always empty #1162
Comments
Hopefully I can figure out a workaround with cdp and the webdriver logs before I lose my own sanity |
This is an issue with Selenium. this issue has been discussed and they are not including support for this. |
Hey @asulwer ! We're aware that it's a selenium issue 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 |
another post states that it isn't possible with chromedriver but with firefox it is? i 'briefly' made an attempt at this with no success. https://stackoverflow.com/questions/6509628/how-to-get-http-response-code-using-selenium-webdriver |
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: