Browser wrongly detected as Chrome instead of Edge due to 'Sec-Ch-Ua' field un http request header

Attaching the screenshot

Hi @autotest2 and @qa scope

Thanks for the details and screenshot!I tested the same scenario on my side and the request headers were showing Microsoft Edge correctly, so in a normal environment everything works as expected.

From what you’ve captured, I believe the difference you’re seeing is not because Edge is broken or because the documentation is unclear, but likely because something in your environment is affecting the headers before they reach the server or are logged.

From my research, modern browsers use a mechanism called User-Agent Client Hints to send browser identity information in structured headers like Sec-CH-UA. This is the replacement for the old single User-Agent string and is designed to be privacy-friendly while still allowing sites to detect the browser brand (e.g., Edge).

Under normal conditions, a browser like Edge includes its brand (for example, "Microsoft Edge") in these client hint headers. That’s what my test showed when I browsed the same type of pages.

In your case, it looks like the header values you captured don’t clearly show “Microsoft Edge” even though you’re using Edge that suggests something external in your environment may be modifying, stripping, or reducing those headers before they’re sent or logged. This could be caused by:

• Enterprise or group policies applied to the browser (which can alter or suppress header values)
• Security or privacy extensions that rewrite or remove headers
• A network proxy, firewall, or appliance that rewrites or strips headers
• Local security/privacy software or browser flags affecting what headers are sent

When any of those are in play, the Sec-CH-UA and related client hints can look different than expected, and it can appear as if a browser is being detected as Chrome/Chromium instead of Edge.

To help narrow down the cause, perhaps you could try some of these suggestions:

1) Check Edge policies

• Open edge://policy in the address bar.
• Look for any policies that might affect user-agent behavior, client hints, or header modifications.

2) Try a clean browser profile

• Create a new Edge profile with default settings.
• Test the same site again to see if the issue persists.

3) Temporarily disable security/privacy software

• Security suites, endpoint protection, or privacy tools can rewrite or strip headers.
• Temporarily disable them and test again.

4) Check the network path

• Confirm whether there is a proxy, firewall, or network filter in the path that could be modifying headers.
• This includes corporate gateways or managed network devices.

Hope this helps! If you have any questions, please feel free to comment below. I'll be happy to assist!