Conversation
|
|
||
| Changing browser fingerprints can be a tedious job. Luckily, Apify SDK provides this feature out of the box with zero configuration necessary. Let's take a look at how it is done. | ||
|
|
||
| Changing browser fingerprints is available in `PuppeteerCrawler` and `PlaywrightCrawler`. You have to pass the `useFingerprints` option to the `browserPoolOptions`. |
There was a problem hiding this comment.
formatting and indenting is messed up in this file, also lets use the same code style in examples as in the rest of the docs and codebase:
- spaces inside object literals
{ ... } - space after
:(e.g.browserPoolOptions: {) - trailing commas
- single quotes
| TODO: this is only for browser-based scraping. We should reflect in the name somehow... IMHO, browser fingerprinting does not remember that it reduces blocking. | ||
|
|
||
|
|
||
| Your scraper might get blocked for numerous reasons. Let's narrow it down to two main reasons. The first one is a bad or blocked IP address. This topic is covered in the [proxy management guide](proxy_management.MD). The second reason we will explore more is browser fingerprints or signatures. |
There was a problem hiding this comment.
Better to use we/our then you/your, or even just A scraper might or Scrapers might.
also the link is wrong, .MD vs .md
| const { hideWebDriver, ...newStealthOptions } = this.stealthOptions; | ||
|
|
||
| log.deprecated( | ||
| 'Puppeteer "stealth" and "stealthOptions" is deprecated' |
There was a problem hiding this comment.
are deprecated, also it looks like you are missing a dot and a space in here, this would result in ... is deprecatedYou should ...
| "api/browser-crawler": { | ||
| "title": "BrowserCrawler" | ||
| }, | ||
| "api/browser-plugin": { | ||
| "title": "BrowserPlugin" | ||
| }, | ||
| "api/cache-container": { | ||
| "title": "CacheContainer" | ||
| }, | ||
| "api/cheerio-crawler": { | ||
| "title": "CheerioCrawler" | ||
| }, | ||
| "api/configuration": { | ||
| "title": "Configuration" | ||
| }, | ||
| "api/cookie-parse-error": { | ||
| "title": "CookieParseError" | ||
| }, | ||
| "api/dataset": { | ||
| "title": "Dataset" | ||
| }, | ||
| "api/exports": { | ||
| "title": "exports" |
There was a problem hiding this comment.
Not sure what this is, but it feels wrong :)
There was a problem hiding this comment.
i dont think it matters much, this is just some translation file
(but its indeed weird)
There was a problem hiding this comment.
I don't even know where it came from. I remember running only generate and start commands.
|
@B4nan Do you know how to edit the examples? I want to add the deprecation notice also to the stealth example. |
|
Check the generate script, its in another repo |
|
Is this still draft on purpose? One small thing I am missing are |
3 participants
No description provided.