Make Access-Control-Allow-Methods matching in CORS preflight spec conformant
Jump to overview

Policy overview

Key metadata and intent for this policy.

Category
Microsoft Edge WebView2 > Network settings
Supported on
Microsoft Edge version 123, Windows 7 or later

Supported OS tags: Windows7

This policy controls whether request methods are uppercased when matching with Access-Control-Allow-Methods response headers in CORS preflight. If you disable this policy, request methods are uppercased. This is the behavior on or before Microsoft Edge 108. If you enable or don't configure this policy, request methods aren't uppercased, unless matching case-insensitively with DELETE, GET, HEAD, OPTIONS, POST, or PUT. This would reject fetch(url, {method: 'Foo'}) + "Access-Control-Allow-Methods: FOO" response header, and would accept fetch(url, {method: 'Foo'}) + "Access-Control-Allow-Methods: Foo" response header. Note: request methods "post" and "put" aren't affected, while "patch" is affected. This policy is intended to be temporary and will be removed in the future.

Internal name
AccessControlAllowMethodsInCORSPreflightSpecConformant
Policy ID
0c8ecdced435
Elements
0

Registry values

How enabled and disabled states update the registry.

ScopeRegistry locationTypeEnabled valueDisabled valueCopy
Path
Software\Policies\Microsoft\Edge\WebView2
Value name
AccessControlAllowMethodsInCORSPreflightSpecConformant
REG_DWORD
HKLM
1
HKCU
1
HKLM
0
HKCU
0
Registry location
Type REG_DWORD · Both
Path
Software\Policies\Microsoft\Edge\WebView2
Value name
AccessControlAllowMethodsInCORSPreflightSpecConformant
Hive
HKLM
Enabled value
1
Disabled value
0
Hive
HKCU
Enabled value
1
Disabled value
0

Policy elements

Inputs and configuration options exposed by this policy.

This policy has no additional user input fields.