[Bug]: Context cookies not sent when using page.request.get()

[niicojs]

Version

1.59.1

Steps to reproduce

I'm using page.request.get to get JSON data, but cookies are not sent along the request.
I have to use the following code to make it work :

  const http_get = async (url: string) => {
    const cookies = await page.context().cookies(url);
    const data = await page.request.get(url, {
      headers: { Cookie: cookies.map((c) => `${c.name}=${c.value}`).join('; ') },
    });
    return await data.json();
  };

Expected behavior

page.request.get should send the current context cookie as state in the doc.

Actual behavior

Cookie are not sent.

Additional context

No response

Environment

Windows using node and pnpm.
"playwright-chromium": "^1.59.1"

  System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H
    Memory: 2.96 GB / 15.73 GB
  Binaries:
    Node: 24.14.1 - C:\Users\nico\.vite-plus\js_runtime\node\24.14.1\node.EXE
    npm: 11.11.0 - C:\Users\nico\.vite-plus\js_runtime\node\24.14.1\npm.CMD
    pnpm: 10.33.0 - D:\.bin\.pnpm\pnpm.CMD
    bun: 1.3.11 - C:\Users\nico\.bun\bin\bun.EXE
  npmPackages:
    playwright-chromium: ^1.59.1 => 1.59.1

[yury-s]

Please share complete repro.

[gaya3bollineni]

This is expected behavior.
page.request is not context‑bound. It creates a standalone APIRequestContext and does not automatically include cookies or storage state from the browser context. Because of that, cookies won’t be sent unless they are manually added to the request headers.
If the request is meant to behave like a browser request and reuse the current session (cookies, auth, storage state), it needs to be made using the context‑bound request API instead.

const http_get = async (url: string) => {
const response = await page.context().request.get(url);
return response.json();
};

[niicojs]

Thanks @gaya3bollineni.
It makes sense, and it works fine.

However, that is not how I understand the doc here: https://playwright.dev/docs/api/class-apirequestcontext.

APIRequestContext returned by browserContext.request and page.request shares cookie storage with the corresponding BrowserContext.

It doesn't say anything about the need to call .context().request instead of just .request.

I'm guessing either the doc or the api needs to be updated.

[gaya3bollineni]

I can see how the wording could be read that way. My understanding is that the APIRequestContext is owned by the BrowserContext, with page.request acting as a convenience accessor. A brief clarification in the docs might help make that relationship clearer,if this understanding is correct