-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Feature]: Add a way to block all cookies and site data in headless mode puppeteer/chromium #3212
Comments
You can try setting |
When enabling "Block all cookies" the first listing might time out but from there its smooth sailing. I've able to run it on already "banned/403'ed" IP's for days now. If possible, I would actually suggest modifying the |
Is there an argument or a function we can add to puppeteer to do this? There has to be some kind of call to set UI settings via API. |
I get a ERR_HTTP2_PROTOCOL_ERROR when checking Nvidia store stock. I think that this would be resolved if I could clear all cookies/cache. I have tried incognito mode, and no luck. |
Proposed solution
I am consistently able to avoid getting 403ed on newegg as long as I block all cookies and delete site data on chromium when i first start running it.
This is a theory so take it with a grain of salt, but I've noticed that newegg allows you to visit their website one time with any IP, and as long as you don't store and block all cookies it seem to think it is always your first visit and wont give you a captcha or 403 you on your next scrape/refresh.
The issue is that it requires headless=false and settings are not persistent. If you can add or inform me of a way to modify chromium user settings to make them persistent and run in headless mode that would be perfect.
Objective
N/A
Goals
N/A
Non-goals
N/A
Anti-goals
N/A
The text was updated successfully, but these errors were encountered: