Jens Laufer
writes about Software Development, Data Science, Entrepreneurship, Traveling and Sports

How You Avoid Being Blocked While Scraping Websites with Proxies

Different approaches that help you with few changes in code

The last hours I had written a scraper to pull the products of an internet marketplace for a niche analysis. The scraper required some effort because the website uses JavaScript for rendering, so a lot of code is executed in the browser. This circumstance increases the effort needed for scraping a website. The use of Selenium with a headless chrome browser finally brought success. Now the moment of truth came, I wanted to pull raw data on a big scale for the first time. I started my scraper, which was supposed to pump the pages into my MongoDB database. Soon I would be able to analyze data, leaving the annoying scraping behind me. Once you have the raw data, that’s half the battle, extracting the interesting fields is the easier part. Because of the parallel processing, the whole thing should be quite fast. While I waited it happened: The size of the files was suddenly always the same and much smaller than at the beginning and…

Http Status code: 429

I realized what had happened: I had been blocked. Of course, I had been aware of this danger from the beginning; however, I had been too impatient. While blocks are often temporary, they prevent you from dragging the amount of data you want. Especially with parallel processing, the danger is severe. You should also be aware that you can get a lifetime block if you commit repeated violations.

You are now asking yourself what exactly must be done to avoid blocking. The answer is simple: You have to use as many different IP addresses as possible from different, worldwide distributed subnets. In an ideal world, I would make every access from a different IP address. This is difficult to realize or would involve a massive effort. In the following, I would like to introduce you to different approaches:

The naive approach

An idea is to use freely available proxies, which you probably already use to hide your IP address. I’m sorry to disappoint you because this won’t get you anywhere. Many of these proxies are no longer available after some time, or they are extremely slow. Besides, you’re not the only one in the world with this idea. Most of the time, you won’t get your requests through these proxies.

The Sledgehammer approach

When I first faced the problem, I had the idea of setting up my own proxy farm using cloud services such as AWS, Azure or GCloud. However, when I did the calculations, I soon realized that this could only be done at very high costs. Let’s assume you want to pull data from a website in 20 threads in parallel and randomly rotate 10 IP addresses for each thread, then you need 200 IP addresses and corresponding server resources. This is cost-intensive, and must also include the effort required to maintain this infrastructure. On AWS, an IP address costs about 4 EUR per month. Together with the server, you will make 800-1000 EUR, plus the effort for the maintenance of your system.

Use Commercial Proxylists

Another possibility is the purchase of commercial proxy lists. You pay a monthly fee and get access to several proxies that you use for scraping. This works very well, but you have to change your code. The effort is limited, but I don’t like the fact that I have to keep the proxy lists somewhere. If I change my contract because I need more proxies, then I have to update my local list. Sure, you can store this in a separate library, but it is a little bit unattractive. For a long time, I have used Bonanza Proxies and have stored the proxy list in a Python module under scrpproxies on Github. The proxies of Bonanza work very well, but I never really liked to have my own library for the proxy lists. If I am honest, I am not interested in the exact IP addresses, and I don’t want to maintain code for something like that.

Here is a small code example to send a request with a proxy. I initialize the proxy service from my module first. The module randomly selects a proxy address, which I then use for the request.

from scrpproxies import proxy
import requests

# Initialization of proxy service with credentials
proxies = proxy.BonanzaProxy(username, password)

# Get returns random proxy ip address
proxy = proxies.get()['http']

# use proxy for the request
r = requests.get(url, proxies={"http": proxy})

Proxies via API call

A bit more elegant are APIs that return a proxy address. The beautiful thing is that you don’t have to keep local proxy lists. You submit a request and get IP addresses which you then use. Luminati is one such service, but I have only used it for a short time.

This is much more elegant than the previous solution but has a disadvantage. You submit a request to obtain IP addresses, which you then use for the actual request. So you make two requests instead of one. Code-wise this requires a little bit of boilerplate code, but it is manageable.

import requests

# Api call to get Proxy
proxy = requests.get(f"{api_key}").text

# use proxy for the request
r = requests.get(url, proxies={"http": proxy})

Black box request handling

A much better approach is that you let a service completely handle the request. A subtle side effect of this method is that you don’t even have to do the heavy lifting of executing JavaScript locally with e.g. Selenium, as the outside service does that. You pass the target URL to the API provider and the API provider processes the call. You can concentrate on extracting the data you need. You’re saving an enormous amount of time. For a long time, I have been looking for such an API. Finally, I found what I was looking for: ScraperAPI offers exactly the features I have always been looking for.

import requests

# Scraper Api url template
SCRAPER_API_URL = "{api_key}&url={url}"

# target url
url = ""

# parsed request url
scraper_url = SCRAPER_API_URL.format(api_key=api_key, url=url)

# fetch target url
r = requests.get(scraper_url)

comments powered by Disqus