Attempt to bypass Google's CAPCHA using a third party service #915
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refs #211
Using a proxy or making any "suspicious" request triggers Google's reCAPTCHA v2 (with callback). I'm using https://deathbycaptcha.com/ to try to solve it.
I tested it using a blacklisted proxy, and the integration seems to be working fine. The problem is, Google just sends another CAPTCHA after we solve the first one so I'm not 100% sure if I'm sending the token to the correct endpoint of if Google is rejecting my request for some reason.
Manually solving the CAPTCHA gives the same result.