AccessControlAllowMethodsInCORSPreflightSpecConformant

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

Supported on:

  • Chrome (Windows) since version 109

Description:

This policy controls whether request methods are uppercased when matching with Access-Control-Allow-Methods response headers in CORS preflight.

If the policy is Disabled, request methods are uppercased.
This is the behavior on or before Samsung Browser 108.

If the policy is Enabled or not set, request methods are not 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" are not affected, while "patch" is affected.

This policy is intended to be temporary and will be removed in the future.

true = Do not uppercase request methods except for DELETE/GET/HEAD/OPTIONS/POST/PUT
false = Always uppercase request methods

Supported features:

  • Applied to browser only after restart.
  • Applied at Samsung Browser profile level.

Data type:

Boolean
Windows:REG_DWORD

Windows registry location:

Software\Policies\Samsung\Internet\AccessControlAllowMethodsInCORSPreflightSpecConformant

Example value:

0x00000001

More policies under Network settings: