[Bug]: Support http2 for APIRequestContext/Fetch

[yosom]

Version

1.45.2

Steps to reproduce

I have discovered an issue where the first code, but the second one does not. Please advise on how to proceed as I wish to use route.fulfill().
one:

const { chromium } = require("playwright");

async function main() {
    const browser = await chromium.launch({ headless: false });
    const context = await browser.newContext();

    const page = await context.newPage();


    await page.route('**/*', async (route) => {
        const response = await route.fetch()
        const headers = response.headers()
        const body = await response.body()

        await route.fulfill({
            status: response.status(),
            headers: headers,
            body: body
        });

        return;
    })

    await page.goto('https://www.bitget.com/');
    await new Promise(resolve => setTimeout(resolve, 10000000));

    await browser.close();
}

main();

two

const { chromium } = require("playwright");

async function main() {
    const browser = await chromium.launch({ headless: false });
    const context = await browser.newContext();

    const page = await context.newPage();


    await page.route('**/*', async (route) => {
        const response = await route.fetch()
        const headers = response.headers()
        const body = await response.body()
        route.continue();
        return;
    })

    await page.goto('https://www.bitget.com/');
    await new Promise(resolve => setTimeout(resolve, 10000000));

    await browser.close();
}

main();

Expected behavior

open page

Actual behavior

can`t open

Additional context

No response

Environment

System:
    OS: macOS 14.5
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
    Memory: 58.00 MB / 16.00 GB
  Binaries:
    Node: 20.15.0 - /usr/local/bin/node
    npm: 10.7.0 - /usr/local/bin/npm
  IDEs:
    VSCode: 1.91.1 - /usr/local/bin/code
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    playwright: ^1.45.2 => 1.45.2

[dgozman]

From the team discussion: we should support http2 in the fetch API, and also include some headers supplied by the network stack in Chromium when doing route.fetch().

[mxschmitt]

Investigation notes:

• got supports it via http-wrapper http.Agent
• Axios doesn't support it yet: HTTP/2 support axios/axios#1175
• Node.js 'fetch()' API has experimental API for it: fetch support for HTTP/2 by default nodejs/undici#2750 (comment)

Ideally we migrate to Node.js fetch internally which depends on nodejs/node#43187 and nodejs/undici#2224. This would simplify a lot. Keep supporting https/socks proxies when using a manual http2.connect() requires rewriting the proxy logic, since http2 doesn't support the http.Agent interface.

Marking it as a feature request for now to collect feedback / to see the demand for it.