You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the default options, as the docs describe, without defining an origin, the response will set Access-Control-Allow-Origin to the request Origin header.
Enable cors with default options:
origin: request Origin header
But if hit with a request that sets Origin: null, then the response will be Access-Control-Allow-Origin: null.
When using the default options, as the docs describe, without defining an
origin
, the response will setAccess-Control-Allow-Origin
to the requestOrigin
header.But if hit with a request that sets
Origin: null
, then the response will beAccess-Control-Allow-Origin: null
.There's a lot of sources that say don't do this...
https://w3c.github.io/webappsec-cors-for-developers/#avoid-returning-access-control-allow-origin-null
I'm not really an expert in this area, but would there be a better default behavior than..
... if the requestOrigin were null?
The text was updated successfully, but these errors were encountered: