Skip to content

[Problem/Bug]: Webview2 Origin header is dropped after a same-origin redirect since the Oct 16 minor release #5781

Open

Description

@bchen-hs-eng

What happened?

Since https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#version-1550428362-october-16-2026-stable, on WebView2, the Origin header is dropped after a same-origin to cross-origin redirect during a SSO sign-in.

We observed this issue on the WebView2 instance consumed by the New Outlook for Windows (on evergreen WebView2 runtime)

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

155.0.4283.62

SDK Version

No response

Framework

Win32

Operating System

Windows 11

OS Version

No response

Repro steps

  • Create a SSO sign in flow that started from app.myapp.com as an example
  • Initial the SSO flow, and redirect to api-app.myapp.com (say to handle CSRF echo)
  • Inspect the resources from api-app.myapp.com -> Origin is no longer present

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

Runtime 155.0.4283.45

Activity

  1. changed the title [-][Problem/Bug]: Webview2 Origin header is dropped after a subdomain redirect since the Oct 16 minor release[/-] [+][Problem/Bug]: Webview2 Origin header is dropped after a same-origin redirect since the Oct 16 minor release[/+] on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't workingregressionSomething used to work but doesn't anymore

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions