[Problem/Bug]: WebView2 makes background requests to certain set of endpoints

[szanto90balazs]

What happened?

WebView2 makes a background requests to:

http://static.edge.microsoftapp.net:443

https://static.edge.microsoftapp.net/default/cloud_config_observers.json

http://edge-mobile-static.azureedge.net:443

http://edge-cloud-resource-static.azureedge.net:443

https://edge-cloud-resource-static.azureedge.net/default/operation_config/default.json

https://edge-mobile-static.azureedge.net/eccp/get

This request started appearing since Edge Canary version 134.0.3092.0 in our automated tests ran against pre-release Edge channels. It's not a feature that is enabled in WebView2 and it is sensitive from a privacy perspective. Can this be removed?

Here are previous tickets raised to disable network requests:
#4180
#2671
#5047

• this was fixed in 134.0.3092.0 but new ones got introduced

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

134.0.3092.0 Canary

SDK Version

1.0.2792.45

Framework

WPF

Operating System

Windows 10, Windows 11

OS Version

No response

Repro steps

Start Fiddler or a similar MITM proxy
Run an app that uses WebView2 with the Canary or Dev runtime version. If re-running an existing app make sure to delete the bin folder so the webview2 profile is deleted.
As soon as the app starts and a navigation request is made a call will be made to:

http://static.edge.microsoftapp.net:443

https://static.edge.microsoftapp.net/default/cloud_config_observers.json

http://edge-mobile-static.azureedge.net:443

http://edge-cloud-resource-static.azureedge.net:443

https://edge-cloud-resource-static.azureedge.net/default/operation_config/default.json

https://edge-mobile-static.azureedge.net/eccp/get

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer SDK

Last working version (if regression)

134.0.3088.0

[avendel]

Unexpected network connections still being established in 135.0.3131.0.

[dhveerap]

We identified the commit causing these network calls, will update here once the fix is available in versions >=134.