proxy_rules
Send specific destination hosts through specific proxies.
Use it for: Scrapers that want an expensive exit only where it matters: residential for the target site, a cheaper proxy for images, CDNs and APIs, or a different country per host.
Browsers: Google Chrome, Microsoft Edge, Brave, Opera, Naver Whale, Yandex Browser, Chromium, Patchright, Rebrowser, Camoufox, Firefox, WebKit.
Details
- Type:
array - Default: none
- Example:
{"proxy_rules":[{"name":"dc-assets","hosts":["*.cloudfront.net","static.example.com"],"proxy":["http://u:[email protected]:4444","http://u:[email protected]:4444"]}]}
A list of { "name": "…", "hosts": [...], "proxy": "…" | [...] } rules. Requests to a host matching a rule use that rule's proxy (round-robin when it is a list); every other host uses proxy. Host patterns support * wildcards, e.g. *.cdn.example.com or static.*. The optional name (up to 64 characters) labels the rule's traffic on your dashboard's Proxy traffic page and in its CSV export.
Needs proxy to be set as the default route. Rules route through a proxy only; routing a host with no proxy (direct from our servers) is not available. The first matching rule wins — keep rules from overlapping so traffic is attributed to the right one.
Used in
- Case 51: Cut residential spend: the page on Tier 1, the images on Tier 4, in one session
- Case 7: Different sites, different proxies, one browser: proxy_rules
- Proxy pool with per-host rules
- Residential IPs for one strict host, your own proxy for the rest
All options: launch options.