Target.createBrowserContext with proxyServer parameter not working.

I was trying to test Target.createBrowserContext to see what it does, and can’t seem to find a way to make the proxyServer parameter work. The same proxy works if I set it when launching chrome with the --proxy-server= flag. I tried setting the proxy with and without scheme:// but the ip shown in the website visited with Target.createTarget is always my real ip, not the proxy.

To test it, I am launching chrome with --remote-debugging-port=9222 and then running this nodejs script:

const CDP = require('chrome-remote-interface');

async function start() {
    // get browser target
    const {webSocketDebuggerUrl} = await CDP.Version();
    const browser = await CDP({
        target: webSocketDebuggerUrl
    });
    const {Target} = browser;
    // create new context with proxy
    const {browserContextId} = await Target.createBrowserContext({
        proxyServer: '127.0.0.1:12345'
    });
    // create new target
    const {targetId} = await Target.createTarget({
        url: 'https://icanhazip.com',
        browserContextId
    });
}

start();

Am I using it wrong?

Component	Version
Operating system	Windows 10
Node.js	14.17.5
Chrome/Chromium/…	Chrome 99.0.4844.82 (Official Build) (64-bit)
chrome-remote-interface	0.31.1

Is Chrome running in a container? NO

[cyrus-and]

And I’m afraid I cannot do anything about it either. Closing this, feel free to add more information if you come up with something.

[wxkk]

(Yes the :: was just an error in the message.)

I just tested in linux and it works there. Will try to test on a different windows box and see what happens.