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
I'm getting captcha failures. oddly, 90% of my cinemagoer queries work, but sometimes, I get a 405. When I try the same url in a private browser, it walks me through a javascript heavy captcha.
If this is an 'anti-bot' measure, (seems likely), then one option is to use a scraper proxy. I solved a similar problem this way, and find it works quite well.
You can get a free personal use account at https://scrapeops.io/. Using the proxy, your requests seem to come from different IPs, each with a randomly chosen user-agent.
An example of how that may look using the requests library:
I got around this issue. When I did a massive set of searches, seven got rejected with error 405. When I tried the same searches, even separately, I got error again. I got around this by slightly changing the search, title vis title (year). The altered searches worked. Hereafter, I will use smaller batches to (hopefully) avoid the problem.
Issue description
Getting 405 captcha failure
Version of Cinemagoer, Python and OS
NOTICE: please always try the latest version from the repository before submitting a bug.
Steps to reproduce the issue
Additional details
I'm getting captcha failures. oddly, 90% of my cinemagoer queries work, but sometimes, I get a 405. When I try the same url in a private browser, it walks me through a javascript heavy captcha.
{'errcode': None, 'errmsg': 'None', 'url': 'https://www.imdb.com/find/?q=The+Purge+%282013%29+++++&s=tt', 'proxy': '', 'exception type': 'IOError', 'original exception': <HTTPError 405: 'Not Allowed'>}
I think i need to use the browser cookie extraction code from yt-dlp, and patch that into parser.http.
I did try setting user-agent to see if that would avoid triggering the captcha test, but that didn't work.
for reference this was the monkey patch I tried:
The text was updated successfully, but these errors were encountered: