News for hackers. Stuff that matters.
Re:Bypassing website anti-scraping protections by dvfjsdhgfv on Friday June 01, 2018 @11:27AM (#17206186)
> there are already anti-scraping solutions on the market that can detect its usage based on a variable it puts into the browser's window.navigator property. Thankfully, we have developed a solution which removes the property from the web browser

Does anyone know what exactly the property in question is?

Re:Bypassing website anti-scraping protections by zzzcpan on Friday June 01, 2018 @11:35AM (#17206288)
Re:Bypassing website anti-scraping protections by dvfjsdhgfv on Friday June 01, 2018 @11:51AM (#17206508)
That's why I was wondering. Last time I checked headless Chrome could be pretty reliably detected in a number of ways, as you say. That they mention just one variable seems quite odd, given that they position themselves as specialists in the field.
Re:Bypassing website anti-scraping protections by jardah on Friday June 01, 2018 @11:54AM (#17206558)
The webdriver property is as far as we know the only one that stays different if you use non-headless chrome with puppeteer. Rest can be handled by use of non-headless chrome as mentioned in the article.

But you are right, after reading through it again, this section of the article should be improved.

Re:Bypassing website anti-scraping protections by aruggirello on Friday June 01, 2018 @12:40PM (#17207134)
Is there anything like this to reliably detect Firefox headless?