-
Notifications
You must be signed in to change notification settings - Fork 459
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
Avoid captcha challenges #242
Conversation
SHA1 ciphers seem to be provoking cloudflare captcha challenges. By removing cipher AES128-SHA captchas can be avoided.
Cookie domain has to start with a . otherwise the cookie won’t be properly detected.
- Always mount the adapter but only update ciphers if explicitly enabled. - Remove ECDHE+SHA instead of AES128-SHA since TLSv1.0 ciphers seem to create problems in some cases. (Credit goes to @pro-src) - Support direct and proxy connections by implementing get_connection (Credit goes to @pro-src)
@Anorov could you test and see if you are also no longer seeing a captcha with this latest version? |
N.B. the ciphers were still properly removed
- Remove AES128-SHA ciphers which seem to provoke captchas if python is linked against openssl < 1.1.1
@Anorov, @pro-src Please review and let me know what you think. Confirmed to work with the following configurations:
|
LGTM As a side note, I don't really like the name of the adapter's class either but I haven't been able to come up with anything much better. Thanks for this! |
@Anorov If you find this solution acceptable and decide to merge the pull request, please squash the commits so the history is not polluted. |
SHA1 ciphers seem to be provoking cloudflare captcha challenges.
By removing cipher AES128-SHA captchas can be avoided.