[Problem/Bug]: missing WebResourceRequest with COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT context

[jls28]

What happened?

For each navigation start event there are generaly
(at least for normal https pages)
a first WebResourceRequest event with context
equal to COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT

That seems perfectly normal and useful,

but when a new page is created via NewWindowRequest/put_NewWindow,
there are a navigation start event but
no WebResourceRequest event with context
equal to COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT.
The document is loaded but the corresponding WebResourceRequest event
is missing.

the documention say :

Other methods which should affect the new web contents like
add_WebResourceRequested have to be called after setting NewWindow (put_NewWindow);

It's exactly what I did.

Importance

Low. My app is not very affected, or this only affects development.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

137.0.3296.93

SDK Version

1.0.2739.15

Framework

Win32

Operating System

Windows 10

OS Version

No response

Repro steps

just code and test.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

[omascia]

For each navigation start event there are generaly
(at least for normal https pages)
a first WebResourceRequest event with context
equal to COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT

The page is not itself a WebResource. I have never been able to setup a AddWebResourceRequestedFilterWithRequestSourceKinds such as to trigger ICoreWebView2WebResourceRequestedEventHandler, for the page itself. I must say that I find this logical though.
How did you set things up to ?

[jls28]

@omascia:
"I have never been able to setup a AddWebResourceRequestedFilterWithRequestSourceKinds such as to trigger ICoreWebView2WebResourceRequestedEventHandler, for the page itself"

This is not what I get.
In my (native win32/64) application, when I perform a webviewWindow->Navigate(url),
there are always a first WebResourceRequest event FOR THIS target URL
with context equal to COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT.
And this seem be exactly the target usage of COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT.
Otherwise for what usage COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT is ?

Have you coded a minimal example ?

[omascia]

Of course, I did. So this is strange and there must be something different between your setup and mine. How did you setup AddWebResourceRequestedFilterWithRequestSourceKinds ? If it works for you and not for me (regarding the document, while I get properly the notifications for everything else), I guess the way of defining the filter plays a role.
Did you explicitely coded a filter for https://* or maybe *.html or what else ?
Did you use COREWEBVIEW2_WEB_RESOURCE_CONTEXT_ALL (I did), or specifically COREWEBVIEW2_WEB_RESOURCE_CONTEXT_DOCUMENT ?

[jls28]

here my code:

CHECK(webView22->AddWebResourceRequestedFilterWithRequestSourceKinds(L"*",
	  COREWEBVIEW2_WEB_RESOURCE_CONTEXT_ALL, COREWEBVIEW2_WEB_RESOURCE_REQUEST_SOURCE_KINDS_ALL));

this code is called only once when the page is created,
into the callbackCreateController;

[omascia]

Same code !! I re-instated it to check again. But same thing: it doesn't get called for the page itself, but only for its resources (the icons, stylesheets, remote javascript, all these things), I can clearly reveal their URLs on each occurence of the event.
But the event is definitely not called for the page itself, in my setup.

	wil::com_ptr<ICoreWebView2WebResourceRequest> request;
	args->get_Request(&request);

	wil::unique_cotaskmem_string co_url;
	request->get_Uri(&co_url);
	std::wstring url(co_url.get());

Oh well, I believe it must work under some specific circumstances, but not mine. Not an issue for me, I need to use the NavigationStarting event anyway, because I have use for the navid integer I get from there. But these findings, yours and mine, do at least prove there is some discrepancy.

Regarding what might be different, I use NavigateWithWebResourceRequest, because I need to pass some HTTP headers (the string headers in following code). And I Navigate to a virtual hostname too.

	wil::com_ptr<ICoreWebView2WebResourceRequest> webResourceRequest;
	CIntegralApp::webviewEnvironment->CreateWebResourceRequest(
		wurl.c_str(), L"GET", nullptr, headers.c_str(), &webResourceRequest);

	HRESULT hr = webview->NavigateWithWebResourceRequest(webResourceRequest.get());

Finally I do register for NavigationStarting, too, as I need it. Maybe if I was not setting up a callback for NavigationStarting I would too see the WebResourceRequest for the page itself. Thinking of it, it could make sense that if the NavigationStarting event is delivered, it doesn't make sense to also notify the same thing through WebResourceRequest... At least, doing what I do, I properly get NavigationStarting for the page, and WebResourceRequests only for the resources pulled by the page itself.

The one thing I can't intercept (but that is not an issue, only a logic discrepancy, is the access to the /navicon.ico by the browser while loading my page. That attempt to access /navicon.ico only happens when Navigating to my Virtual Host, by the way.