[BUG] IP:PORT Proxy doesnt work on playwright-firefox

[sentoxaio]

• Playwright Version: ^1.2.1
• Operating System: Windows
• Node.js version: v14.1.0.
• Browser: Firefox

Code Snippet

options.proxy = {
	server: "<port>:<ip>",
};

await firefox.launch(options)

Orginal Error:

It seems like that ip:port proxies don't work with playwright-firefox.

When you put http:// before it the browser starts, but throws
this error:

[aslushnikov]

@sentoxaio the following works for me (with my personal proxy):

const {chromium, webkit, firefox} = require('playwright');

(async () => {
  const browser = await firefox.launch({
    headless: false,
    proxy: {
      server: 'http://40.112.209.181:3128',
      username: process.env.PROXY_USERNAME,
      password: process.env.PROXY_PASSWORD,
    },
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
})();

Maybe something else is going wrong?

[sentoxaio]

@aslushnikov I am talking about proxies without an authentication (password & username).

[FoonkG]

Indeed, proxies with user:pass authentication work well on playwright-firefox but proxies without user:pass authentication don't.

[aslushnikov]

@sentoxaio, @FoonkG: I tried with a local charles proxy running on localhost:8888 - worked fine:

The script with playwright v1.3.0:

const {chromium, webkit, firefox} = require('playwright');

(async () => {
  const browser = await firefox.launch({
    headless: false,
    proxy: {
      server: 'http://127.0.0.1:8888'
    },
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
})();

Any more details to help me reproduce this?

[aslushnikov]

FYI: current playwright@next has a new proxy implementation for Firefox, so please give it a try - maybe it'll fix things on your end

[pavlealeksic]

The problem also might be not adding http:// in front of the proxy ip:port

[aslushnikov]

Yeah, protocol is pretty important! This way you can specify both regular (HTTP) and Secure (HTTPS) web proxies.

[aslushnikov]

Ah, now I understand! We have a shortform in the documentation that doesn't actually work for firefox. We'll fix this.