Samuel Corso

Hi @labboy0276, yes I noted this issue a couple of weeks ago. I believe that it is a CORS error, and I haven't gotten around to addressing it yet.

@labboy0276 just copying this over here for reference: https://user-images.githubusercontent.com/38767335/125101214-fa64c380-e0a7-11eb-92dd-cbdb50f2e127.png

@labboy0276 have you tested this with the Nike issue? Curious if it might help.

@labboy0276 I added this: ``` await page.setExtraHTTPHeaders({ 'user-agent': `${userAgent}`, 'sec-fetch-dest': 'none', accept: '*/*', 'sec-fetch-site': 'cross-site', 'sec-fetch-mode': 'cors', 'accept-language': 'en-US' }); ``` But it doesn't seem to be doing the trick....

There is a new captcha on the footsites, I've never repro'd it in the browser but I'm curious if this might help reduce bot detection so that we don't hit...

So it looks like, testing with these headers on the footsites, I got blocked. It took me to a Terms of Service page. Testing without them, I hit the captcha...

@Kohlsen yes, that is indeed the common meaning for a 429 response code. I have tried that, among numerous other things, but to no avail. I keep looking at it...

@jhgeluk yes, I think it has something to do with the browser fingerprint and/or the speed of the navigations. I have some potential solutions for this, including: 1. Randomizing all...

@13ROY could you take a look at his when you get a chance?

@jhgeluk yes, the browsing history was a good idea for creating a cookie profile. Have you checked `window.navigator` in the console? These are many of the properties used by fingerprinting...