The right proxy type for Rust reqwest
For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.
- Residentialfrom $2.64 per GB
- Residential Litefrom $0.60 per GB
- Unlimited Datacenterfrom $0.56 per hour
The values to enter in Rust reqwest
Every PiratProxies plan comes down to four values: host, port, username and password. Here they are for Residential; your own username and password are on your plan page.
| Host | resi.piratproxies.com |
|---|---|
| HTTP port | 8080 |
| SOCKS5 port | 1080 |
| Username | USERNAME |
| Password | shown on your plan page |
There is no separate country or session field: both are part of the username. Your plan page has a generator that writes it, and Targeting and sessions describes each piece.
Setting it up in Rust reqwest
- Create the proxy with
Proxy::allso it covers http and https. - Add the login with
basic_auth, then build the client.
Code: Rust reqwest through a proxy
Rust
use reqwest::{Client, Proxy};
#[tokio::main]
async fn main() -> Result<(), reqwest::Error> {
let proxy = Proxy::all("http://resi.piratproxies.com:8080")?.basic_auth("USERNAME", "PASSWORD");
let client = Client::builder().proxy(proxy).build()?;
println!("{}", client.get("https://api.ipify.org").send().await?.text().await?);
Ok(())
}Put your own login from the plan page in place of USERNAME and PASSWORD. The example calls an IP-check service, so what it prints is the address your request came from.
Should Rust reqwest rotate IPs or keep one?
When Rust reqwest is fetching lots of unrelated pages, leave the session out of the username and each request gets a fresh IP address. When requests belong together, such as a login, a basket or paginated results that set cookies, put a session in the username so they all share one address.
Here is what a sticky username looks like:
USERNAME-country-us-time-600-session-a1b2c3d4When Rust reqwest will not connect
- SOCKS5 needs the
socksfeature of reqwest switched on inCargo.toml. - Error
407means the login was refused. Copy the username and password from your plan page once more, and make sure no space crept in and the username was not cut short. - An IP in the wrong country nearly always comes from the username, since the country code lives there. Other fixes.
Rust reqwest and proxies: questions
Can Rust reqwest use a SOCKS5 proxy?
Yes. Point it at port 1080 with the same username and password.
Which PiratProxies plan suits Rust reqwest best?
For most scraping, Residential Lite is the cheapest way to get home IP addresses in the right country. Use Residential when you need a particular state or city, and Unlimited Datacenter for targets in the United States that do not block data centre addresses.
Words used in this guide: web scraping, rotating proxy, sticky session, rate limiting, headless browser.
Rust reqwest belongs to its own developers, and PiratProxies has no connection with them; we name it only to say what this guide covers. Follow the rules of the sites you visit and our acceptable use policy.