NFR: force IP on page.goto

New feature request: force IP on page.goto

In case of blue/green deployment, I would like to test “mywebsite.com” on other IP (next future release is 2.2.2.2).

The dirty hack should edit /etc/hosts…

                  +-----------------+
                  |                 |
                  |  mywebsite.com  |
                  |                 |
                  +-----------------+
+-----------+        Production
| Puppeteer |        1.1.1.1
+-----+-----+
      |
      |           +-----------------+
      |           |                 |
      +---------> |  mywebsite.com  |
                  |                 |
                  +-----------------+
                   Future Production
                   2.2.2.2

Example:

let res = await page.gogo("https://mywebsite.com", {ip: "2.2.2.2"});

[benjaminpwarren]

The host-rules argument appears to solve this for me:

const browser = await puppeteer.launch({
  args: [
    '--host-rules=MAP mysite.com.au 123.456.789.012,MAP mysite2.com.au 123.456.789.012'
  ],
  ignoreHTTPSErrors: true
})

[jots]

This would be super handy for testing site migrations before making the dns change. screenshot pages on the 2 servers and compare them.

Not sure how the proxy solution works, would we need to create a proxy server that knows how to map domains to new IPs? Would be much easier to use the syntax @HanXHX proposes: page.gogo("https://mywebsite.com", {ip: "2.2.2.2"});