Skip to main content

Network

Playwright provides APIs to monitor and modify network traffic, both HTTP and HTTPS. Any requests that page does, including XHRs and fetch requests, can be tracked, modified and handled.


HTTP Authentication

using var context = await Browser.NewContextAsync(new()
{
HttpCredentials = new HttpCredentials
{
Username = "bill",
Password = "pa55w0rd"
},
});
var page = await context.NewPageAsync();
await page.GotoAsync("https://example.com");

API reference

HTTP Proxy

You can configure pages to load over the HTTP(S) proxy or SOCKSv5. Proxy can be either set globally for the entire browser, or for each browser context individually.

You can optionally specify username and password for HTTP(S) proxy, you can also specify hosts to bypass proxy for.

Here is an example of a global proxy:

var proxy = new Proxy
{
Server = "http://myproxy.com:3128",
Username = "user",
Password = "pwd"
};
await using var browser = await BrowserType.LaunchAsync(new()
{
Proxy = proxy
});

When specifying proxy for each context individually, Chromium on Windows needs a hint that proxy will be set. This is done via passing a non-empty proxy server to the browser itself. Here is an example of a context-specific proxy:

var proxy = new Proxy { Server = "per-context" };
await using var browser = await BrowserType.LaunchAsync(new()
{
// Browser proxy option is required for Chromium on Windows.
Proxy = proxy
});
using var context = await Browser.NewContextAsync(new()
{
Proxy = new Proxy { Server = "http://myproxy.com:3128" })
});

Network events

You can monitor all the requests and responses:

using Microsoft.Playwright;

using var playwright = await Playwright.CreateAsync();
await using var browser = await playwright.Chromium.LaunchAsync();
var page = await browser.NewPageAsync();
page.Request += (_, request) => Console.WriteLine(">> " + request.Method + " " + request.Url);
page.Response += (_, response) => Console.WriteLine("<< " + response.Status + " " + response.Url);
await page.GotoAsync("https://example.com");

Or wait for a network response after the button click:

// Use a glob URL pattern
var waitForResponseTask = page.WaitForResponseAsync("**/api/fetch_data");
await page.Locator("button#update").ClickAsync();
var response = await waitForResponseTask;

Variations

// Use a regular expression
var waitForResponseTask = page.WaitForResponseAsync(new Regex("\\.jpeg$"));
await page.Locator("button#update").ClickAsync();
var response = await waitForResponseTask;

// Use a predicate taking a Response object
var waitForResponseTask = page.WaitForResponseAsync(r => r.Url.Contains(token));
await page.Locator("button#update").ClickAsync();
var response = await waitForResponseTask;

API reference


Handle requests

You can mock API endpoints via handling the network requests in your Playwright script.

Variations

await page.RouteAsync("**/api/fetch_data", async route => {
await route.FulfillAsync(status: 200, body: testData);
});
await page.GotoAsync("https://example.com");

API reference


Modify requests

// Delete header
await page.RouteAsync("**/*", async route => {
var headers = new Dictionary<string, string>(route.Request.Headers.ToDictionary(x => x.Key, x => x.Value));
headers.Remove("X-Secret");
await route.ContinueAsync(new RouteContinueOptions { Headers = headers });
});

// Continue requests as POST.
await page.RouteAsync("**/*", async route => await route.ContinueAsync(method: "POST"));

You can continue requests with modifications. Example above removes an HTTP header from the outgoing requests.

Abort requests

await page.RouteAsync("**/*.{png,jpg,jpeg}", route => route.AbortAsync());

// Abort based on the request type
await page.RouteAsync("**/*", async route => {
if ("image".Equals(route.Request.ResourceType))
await route.AbortAsync();
else
await route.ContinueAsync();
});

API reference


Modify responses

To modify a response use APIRequestContext to get original response and then pass the response to Route.FulfillAsync(options). You can override individual fields on the response via options:

await Page.RouteAsync("**/title.html", async route =>
{
// Fetch original response.
var response = await Page.APIRequest.FetchAsync(route.Request);
// Add a prefix to the title.
var body = await response.TextAsync();
body = body.Replace("<title>", "<title>My prefix:");

var headers = response.Headers;
headers.Add("Content-Type", "text/html");

await route.FulfillAsync(new()
{
// Pass all fields from the response.
Response = response,
// Override response body.
Body = body,
// Force content type to be html.
Headers = headers,
});
});

API reference


Record and replay requests

You can record network activity as an HTTP Archive file (HAR). Later on, this archive can be used to mock responses to the network requests. You'll need to:

  1. Record a HAR file.
  2. Commit the HAR file alongside the tests.
  3. Route requests using the saved HAR files in the tests.

Recording HAR with CLI

Open the browser with Playwright CLI and pass --save-har option to produce a HAR file. Optionally, use --save-har-glob to only save requests you are interested in, for example API endpoints. If the har file name ends with .zip, artifacts are written as separate files and are all compressed into a single zip.

# Save API requests from example.com as "example.har" archive.
pwsh bin/Debug/netX/playwright.ps1 open --save-har=example.har --save-har-glob="**/api/**" https://example.com

Recording HAR with a script

Alternatively, instead of using the CLI, you can record HAR programmatically. Pass har option when creating a BrowserContext with Browser.NewContextAsync(options) to create an archive. If the har file name ends with .zip, artifacts are written as separate files and are all compressed into a single zip.

var context = await browser.NewContextAsync(new() {
RecordHarPath = "example.har",
RecordHarUrlFilter = "**/api/**",
});

// ... Perform actions ...

// Close context to ensure HAR is saved to disk.
await context.CloseAsync();

Replaying from HAR

Use Page.RouteFromHARAsync(har, options) or BrowserContext.RouteFromHARAsync(har, options) to serve matching responses from the HAR file.

// Either use a matching response from the HAR,
// or abort the request if nothing matches.
await context.RouteFromHARAsync("example.har");

HAR replay matches URL and HTTP method strictly. For POST requests, it also matches POST payloads strictly. If multiple recordings match a request, the one with the most matching headers is picked. An entry resulting in a redirect will be followed automatically.

Similar to when recording, if given HAR file name ends with .zip, it is considered an archive containing the HAR file along with network payloads stored as separate entries. You can also extract this archive, edit payloads or HAR log manually and point to the extracted har file. All the payloads will be resolved relative to the extracted har file on the file system.


WebSockets

Playwright supports WebSockets inspection out of the box. Every time WebSocket is created, event Page.WebSocket event is fired. This event contains the WebSocket instance for further web socket frames inspection:

page.WebSocket += (_, ws) =>
{
Console.WriteLine("WebSocket opened: " + ws.Url);
ws.FrameSent += (_, f) => Console.WriteLine(f.Text);
ws.FrameReceived += (_, f) => Console.WriteLine(f.Text);
ws.Close += (_, ws1) => Console.WriteLine("WebSocket closed");
};

API reference


Missing Network Events and Service Workers

Playwright's built-in BrowserContext.RouteAsync(url, handler, options) and Page.RouteAsync(url, handler, options) allow your tests to natively route requests and perform mocking and interception.

  1. If you're using Playwright's native BrowserContext.RouteAsync(url, handler, options) and Page.RouteAsync(url, handler, options), and it appears network events are missing, disable Service Workers by setting Browser.newContext.serviceWorkers to 'block'.
  2. It might be that you are using a mock tool such as Mock Service Worker (MSW). While this tool works out of the box for mocking responses, it adds its own Service Worker that takes over the network requests, hence making them invisible to BrowserContext.RouteAsync(url, handler, options) and Page.RouteAsync(url, handler, options). If you are interested in both network testing and mocking, consider using built-in BrowserContext.RouteAsync(url, handler, options) and Page.RouteAsync(url, handler, options) for response mocking.
  3. If you're interested in not solely using Service Workers for testing and network mocking, but in routing and listening for requests made by Service Workers themselves, please see this experimental feature.