wehub-resource-sync
62 lines
3.5 KiB
Plaintext
62 lines
3.5 KiB
Plaintext
---
|
|
id: avoid-blocking
|
|
title: Avoid getting blocked
|
|
description: How to avoid getting blocked when scraping
|
|
---
|
|
|
|
import Tabs from '@theme/Tabs';
|
|
import TabItem from '@theme/TabItem';
|
|
import CodeBlock from '@theme/CodeBlock';
|
|
|
|
import PlaywrightSource from '!!raw-loader!./avoid_blocking_playwright.ts';
|
|
import PuppeteerSource from '!!raw-loader!./avoid_blocking_puppeteer';
|
|
import PlaywrightFingerprintsOffSource from '!!raw-loader!./avoid_blocking_playwright_fingerprints_off.ts';
|
|
import PuppeteerFingerprintsOffSource from '!!raw-loader!./avoid_blocking_puppeteer_fingerprints_off.ts';
|
|
|
|
A scraper might get blocked for numerous reasons. Let's narrow it down to the two main ones. The first is a bad or blocked IP address. You can learn about this topic in the [proxy management guide](./proxy-management). The second reason is [browser fingerprints](https://pixelprivacy.com/resources/browser-fingerprinting/) (or signatures), which we will explore more in this guide. Check the [Apify Academy anti-scraping course](https://docs.apify.com/academy/anti-scraping) to gain a deeper theoretical understanding of blocking and learn a few tips and tricks.
|
|
|
|
Browser fingerprint is a collection of browser attributes and significant features that can show if our browser is a bot or a real user. Moreover, most browsers have these unique features that allow the website to track the browser even within different IP addresses. This is the main reason why scrapers should change browser fingerprints while doing browser-based scraping. In return, it should significantly reduce the blocking.
|
|
|
|
## Using browser fingerprints
|
|
|
|
Changing browser fingerprints can be a tedious job. Luckily, Crawlee provides this feature with zero configuration necessary - the usage of fingerprints is enabled by default and available in `PlaywrightCrawler` and `PuppeteerCrawler`. So whenever we build a scraper that is using one of these crawlers - the fingerprints are going to be generated for the default browser and the operating system out of the box.
|
|
|
|
## Customizing browser fingerprints
|
|
|
|
In certain cases we want to narrow down the fingerprints used - e.g. specify a certain operating system, locale or browser. This is also possible with Crawlee - the crawler can have the generation algorithm customized to reflect the particular browser version and many more. Let's take a look at the examples bellow:
|
|
|
|
<Tabs groupId="avoid_blocking">
|
|
<TabItem value="playwright" label="PlaywrightCrawler" default>
|
|
<CodeBlock language="js">
|
|
{PlaywrightSource}
|
|
</CodeBlock>
|
|
</TabItem>
|
|
<TabItem value="puppeteer" label="PuppeteerCrawler">
|
|
<CodeBlock language="js">
|
|
{PuppeteerSource}
|
|
</CodeBlock>
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
## Disabling browser fingerprints
|
|
|
|
On the contrary, sometimes we want to entirely disable the usage of browser fingerprints. This is easy to do with Crawlee too. All we have to do is set the `useFingerprints` option of the `browserPoolOptions` to `false`:
|
|
|
|
<Tabs groupId="avoid_blocking">
|
|
<TabItem value="playwright" label="PlaywrightCrawler" default>
|
|
<CodeBlock language="js">
|
|
{PlaywrightFingerprintsOffSource}
|
|
</CodeBlock>
|
|
</TabItem>
|
|
<TabItem value="puppeteer" label="PuppeteerCrawler">
|
|
<CodeBlock language="js">
|
|
{PuppeteerFingerprintsOffSource}
|
|
</CodeBlock>
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
**Related links**
|
|
|
|
- [Fingerprint Suite Docs](https://github.com/apify/fingerprint-suite)
|
|
- [Apify Academy anti-scraping course](https://docs.apify.com/academy/anti-scraping)
|