Two Selenium Windows Can Still Share One Proxy Policy
Distinguish a new browser window from a separately configured WebDriver session when testing different proxy routes.
A new window handle is another browsing context in the current WebDriver session, not a new proxy capability set.
| Action | Routing consequence |
|---|---|
| Open another tab/window on one driver | Retains that session's configured proxy policy |
| Create another driver session with its intended options | Provides another independently configured policy |
Keep driver, selected endpoint and observed result together. Separate sessions can isolate cookies/storage, but reusing an account still gives the destination an account-level relationship.
Check exit identity through each intended session. For permitted public-site tests, the free proxy list offers candidates to configure in each session's supported proxy interface. Different proxy endpoints can share an exit, and a provider can rotate an exit behind one unchanged endpoint.
On a remote browser, the configured proxy must be reachable from its host; loopback refers to that browser environment. Standard capabilities offer no per-window setter. Extra browser automation features/extensions need their own supported integration.