Identify network traffic originating from App Guard containers at the proxy level
Microsoft EdgeVersion 91.0.834.0 (Official build) canary (64-bit) The newly added flag for this feature:edge://flags/#edge-wdag-traffic-identification If enabled, Application Guard traffic will be tagged with a X-MS-ApplicationGuard-Initiated header – Windows By the way, if any user or developer is reading this, can you help me understand how exactly we should monitor WDAG connections? There are some difficulties I've been trying to solve in the past few hours.New privacy oriented feature added to Edge 82 - Freeze User-Agent request header
New in Microsoft Edge Version 82.0.421.0 (Official build) canary (64-bit) Reason for doing it is more about privacy and stopping fingerprinting. edge://flags/ Freeze User-Agent request header Set the User-Agent request header to a static string that conforms to the current User-Agent string format but only reveals desktop vs Android and if the 'mobile' flag is set – Mac, Windows #freeze-user-agent to be more effective, also enable this flag: Reduce default 'referer' header granularity If a page hasn't set an explicit referrer policy, setting this flag will reduce the amount of information in the 'referer' header for cross-origin requests. – Mac, Windows #reduced-referrer-granularity More info: https://www.chromestatus.com/feature/5704553745874944 https://css-tricks.com/freezing-user-agent-strings/
