You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sources/academy/webscraping/anti_scraping/techniques/firewalls.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ One of the most common WAFs one can come across is the one from [Cloudflare](htt
19
19
20
20
## How it works {#how-it-works}
21
21
22
-
WAPs work on a similar premise as regular firewalls. Web admins define the rules, and the firewall executes them. As an example of how the WAF can work, we will take a look at Cloudflare's solution:
22
+
WAFs work on a similar premise as regular firewalls. Web admins define the rules, and the firewall executes them. As an example of how the WAF can work, we will take a look at Cloudflare's solution:
23
23
24
24
1. The visitor sends a request to the webpage.
25
25
2. The request is intercepted by the firewall.
@@ -38,7 +38,7 @@ Since there are multiple providers, it is essential to say that the challenges a
38
38
- Overriding the browser's [fingerprint](./fingerprinting.md) (most effective).
39
39
- Farming the [cookies](../../../glossary/concepts/http_cookies.md) from a website with a headless browser, then using the farmed cookies to do HTTP based scraping (most performant).
40
40
41
-
As you likely already know, there is no solution that fits all. If you are struggling to get past a WAP provider, you can try using Firefox with Playwright.
41
+
As you likely already know, there is no solution that fits all. If you are struggling to get past a WAF provider, you can try using Firefox with Playwright.
0 commit comments