Skip to content

docs: clarify tieredProxyUrls behavior for standalone newUrl() calls #3666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
okwn wants to merge 1 commit into from
+4 −2
Closed

docs: clarify tieredProxyUrls behavior for standalone newUrl() calls #3666

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/guides/proxy_management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,11 @@ You can also provide a list of proxy tiers to the `ProxyConfiguration` class. Th

:::warning

Note that the `tieredProxyUrls` option requires `ProxyConfiguration` to be used from a crawler instance ([see below](#crawler-integration)).
The `tieredProxyUrls` option requires `ProxyConfiguration` to be used from a crawler instance ([see below](#crawler-integration)).

Using this configuration through the `newUrl` calls will not yield the expected results.
Calling `newUrl()` or `newProxyInfo()` directly on the `ProxyConfiguration` object will not activate tier logic — it will simply rotate through all provided URLs in round-robin fashion, ignoring tier associations and blocking detection. This is because tiered proxy behavior relies on session state and per-domain error tracking that only exist within a running crawler.

For standalone usage, use `proxyUrls` (simple rotation) instead, or use `newUrlFunction` to implement custom logic.

:::

Expand Down