Setting a WebView2 UserAgent isn't updated in the NavigationStarting event
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 28.000000000000004%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Shipwreck Software
0
Reputation points
I'm creating a simple C# WinUI3 app that uses WebView2 to connect to OpenStreetMaps. When I set a custom UserAgent on the WebView2.CoreWebView2, it doesn't get reflected in the RequestHeaders in the CoreWebView2NavigationStartingEventArgs object in the NavigationStarting event.
It's critical that I verify that I'm actually set the user agent (it's a requirement using OpenStreetMaps that I have a custom User-Agent in the headers).
What I expected is that when I look at the headers, the user-agent is set correctly. What I actually see is the default User-Agent (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.0)
Windows development | Windows App SDK
{count} votes
-
Viorel 123.6K Reputation points2025-07-29T23:40:09.3833333+00:00 What problems does this defect generate?
-
Shipwreck Software 0 Reputation points
2025-07-30T01:02:10.8966667+00:00 The problem this generates is that it wastes my time! What should have been a simple "set this value and then verify it" turned in a giant crappy experience.
It also continues to confirm the obvious: that many normal programming experiences on Windows require more time and effort than should be needed. The API is full of friction points that should never have existed.
-
Viorel 123.6K Reputation points
2025-07-30T06:51:30.2+00:00 Probably this issue, accompanied by sufficient code details, can be reported here:
However, maybe the NavigationStarting is the place where the User Agent can be set:
Sign in to comment
Sign in to answer