Skip to main content

WebSocketRoute

Whenever a WebSocket route is set up with Page.RouteWebSocketAsync() or BrowserContext.RouteWebSocketAsync(), the WebSocketRoute object allows to handle the WebSocket, like an actual server would do.

Mocking

By default, the routed WebSocket will not connect to the server. This way, you can mock entire communcation over the WebSocket. Here is an example that responds to a "request" with a "response".

await page.RouteWebSocketAsync("wss://example.com/ws", ws => {
  ws.OnMessage(message => {
    if (message == "request")
      ws.Send("response");
  });
});

Since we do not call WebSocketRoute.ConnectToServer inside the WebSocket route handler, Playwright assumes that WebSocket will be mocked, and opens the WebSocket inside the page automatically.

Here is another example that handles JSON messages:

await page.RouteWebSocketAsync("wss://example.com/ws", ws => {
  ws.OnMessage(message => {
    using var jsonDoc = JsonDocument.Parse(message);
    JsonElement root = jsonDoc.RootElement;
    if (root.TryGetProperty("request", out JsonElement requestElement) && requestElement.GetString() == "question")
    {
      var response = new Dictionary<string, string> { ["response"] = "answer" };
      string jsonResponse = JsonSerializer.Serialize(response);
      ws.Send(jsonResponse);
    }
  });
});

Intercepting

Alternatively, you may want to connect to the actual server, but intercept messages in-between and modify or block them. Calling WebSocketRoute.ConnectToServer returns a server-side WebSocketRoute instance that you can send messages to, or handle incoming messages.

Below is an example that modifies some messages sent by the page to the server. Messages sent from the server to the page are left intact, relying on the default forwarding.

await page.RouteWebSocketAsync("/ws", ws => {
  var server = ws.ConnectToServer();
  ws.OnMessage(message => {
    if (message == "request")
      server.Send("request2");
    else
      server.Send(message);
  });
});

After connecting to the server, all messages are forwarded between the page and the server by default.

However, if you call WebSocketRoute.OnMessage() on the original route, messages from the page to the server will not be forwarded anymore, but should instead be handled by the handler.

Similarly, calling WebSocketRoute.OnMessage() on the server-side WebSocket will stop forwarding messages from the server to the page, and handler should take care of them.

The following example blocks some messages in both directions. Since it calls WebSocketRoute.OnMessage() in both directions, there is no automatic forwarding at all.

await page.RouteWebSocketAsync("/ws", ws => {
  var server = ws.ConnectToServer();
  ws.OnMessage(message => {
    if (message != "blocked-from-the-page")
      server.Send(message);
  });
  server.OnMessage(message => {
    if (message != "blocked-from-the-server")
      ws.Send(message);
  });
});

Methods​

CloseAsync​

Added in: v1.48 webSocketRoute.CloseAsync

Closes one side of the WebSocket connection.

Usage

await WebSocketRoute.CloseAsync(options);

Arguments

Returns

ConnectToServer​

Added in: v1.48 webSocketRoute.ConnectToServer

By default, routed WebSocket does not connect to the server, so you can mock entire WebSocket communication. This method connects to the actual WebSocket server, and returns the server-side WebSocketRoute instance, giving the ability to send and receive messages from the server.

Once connected to the server:

  • Messages received from the server will be automatically forwarded to the WebSocket in the page, unless WebSocketRoute.OnMessage() is called on the server-side WebSocketRoute.
  • Messages sent by the WebSocket.send() call in the page will be automatically forwarded to the server, unless WebSocketRoute.OnMessage() is called on the original WebSocketRoute.

See examples at the top for more details.

Usage

WebSocketRoute.ConnectToServer

Returns

OnClose​

Added in: v1.48 webSocketRoute.OnClose

Allows to handle WebSocket.close.

By default, closing one side of the connection, either in the page or on the server, will close the other side. However, when WebSocketRoute.OnClose() handler is set up, the default forwarding of closure is disabled, and handler should take care of it.

Usage

WebSocketRoute.OnClose(handler);

Arguments

  • handler Action<int?, string>#

    Function that will handle WebSocket closure. Received an optional close code and an optional close reason.

OnMessage​

Added in: v1.48 webSocketRoute.OnMessage

This method allows to handle messages that are sent by the WebSocket, either from the page or from the server.

When called on the original WebSocket route, this method handles messages sent from the page. You can handle this messages by responding to them with WebSocketRoute.Send(), forwarding them to the server-side connection returned by WebSocketRoute.ConnectToServer or do something else.

Once this method is called, messages are not automatically forwarded to the server or to the page - you should do that manually by calling WebSocketRoute.Send(). See examples at the top for more details.

Calling this method again will override the handler with a new one.

Usage

WebSocketRoute.OnMessage(handler);

Arguments

Send​

Added in: v1.48 webSocketRoute.Send

Sends a message to the WebSocket. When called on the original WebSocket, sends the message to the page. When called on the result of WebSocketRoute.ConnectToServer, sends the message to the server. See examples at the top for more details.

Usage

WebSocketRoute.Send(message);

Arguments

Url​

Added in: v1.48 webSocketRoute.Url

URL of the WebSocket created in the page.

Usage

WebSocketRoute.Url

Returns