[Problem/Bug]: Argument --remote-allow-origins not allowing remote connection

[raffaeler]

What happened?

I am using the latest 134 release of the WebView and tried to open the CDP traffic setting the environment variable:

WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--remote-debugging-port=9224 --remote-allow-origins=* "

or

WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--remote-debugging-port=9224 --remote-allow-origins=ip_address "

In both cases, using netstat, the port 9224 is only opened on localhost.

Is this a bug, a wrong configuration or a missing flag?

Thank you

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

134.0.3124.72

SDK Version

No response

Framework

Other

Operating System

Windows 10

OS Version

No response

Repro steps

I tested the scenario on multiple installations and even with edge.exe I obtain the same result.

Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

[rprakash648]

I am also facing an same issue with Microsoft Edge 134 and unable to connect with --remote-debugging-port=9220 and getting an error message

selenium.common.exceptions.TimeoutException: Message: timeout: Timed out receiving message from renderer: 600.000