A Chromiumoxide Page Must Belong to the Proxy Context

Create the page in its proxy-configured Chromiumoxide context by passing the context ID to the page target.

For Chromiumoxide 0.9.1, inside the application’s existing asynchronous browser lifecycle:

use chromiumoxide::cdp::browser_protocol::target::{
    CreateBrowserContextParamsBuilder, CreateTargetParams,
};

let context_id = browser.create_browser_context(
    CreateBrowserContextParamsBuilder::default()
        .proxy_server("http://proxy.example:8080")
        .build()
).await?;

let mut target = CreateTargetParams::new("about:blank");
target.browser_context_id = Some(context_id.clone());
let page = browser.new_page(target).await?;

The browser is already connected or launched, and its handler must keep being polled. Propagate errors through the enclosing async function, then navigate with page.

Keep the context alive until its pages finish, and dispose it through browser.dispose_browser_context during cleanup. The context’s proxy_server selects the endpoint. For permitted public browsing, an HTTP URL built from the HTTP proxy list can fill that field; proxy authentication still needs its own challenge handling.