[Bug]: WebView2 WebResourceRequested does not fired for WebSockets

What happened?

Hi,

I'm using WebView2 in custom WFP application. I need to add custom headers into requests so I use WebResourceRquested event. Here is my code:

`using Microsoft.Web.WebView2.Core;
using Microsoft.Web.WebView2.Wpf;

namespace WebViewAddingHeaders;
internal class MyWebBrowser: WebView2
{
public MyWebBrowser()
{
CoreWebView2InitializationCompleted += OnInitializationCompleted;
}

private void OnInitializationCompleted(object? sender, CoreWebView2InitializationCompletedEventArgs e)
{
	CoreWebView2.AddWebResourceRequestedFilter("*", CoreWebView2WebResourceContext.All);
	CoreWebView2.WebResourceRequested += CoreWebView2_WebResourceRequested;
}

private void CoreWebView2_WebResourceRequested(object? sender, CoreWebView2WebResourceRequestedEventArgs e)
{
	e.Request.Headers.SetHeader("MY_TESTING_HEADER", "Testing header value");
}

}`

But I noticed that this event is not fired for web sockets. I try to access python + streamlit application. There are sent multiple requests. For "normal" requests the header is present.

But it is not present for web sockets

I tried to filter only WebSockets in AddWebResourceRequestedFilter. I tried to enable custom scheme for ws. But nothing helped.

Is it possible to catch and enhance all requests, including web sockets?

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

1.0.2210.55

SDK Version

No response

Framework

WPF

Operating System

Windows 11

OS Version

No response

Repro steps

In description.

Repros in Edge Browser

No

Regression

No, this never worked

Last working version (if regression)

No response

AB#48649859

Start with the WPF repro in the issue, focusing on CoreWebView2.AddWebResourceRequestedFilter and the WebResourceRequested event. Verify the behavior for WebSocket requests using the stated WebView2 runtime and compare it with normal requests. Done means determining whether WebSocket requests can be intercepted and have headers added, or documenting the supported limitation.