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
The standard forbids using * in the Access-Control-Allow-Origin, Access-Control-Expose-Headers, Access-Control-Allow-Methods, or Access-Control-Allow-Headers response header, if the Access-Control-Allow-Credentials request header is set to true.
The standard forbids using
*
in theAccess-Control-Allow-Origin
,Access-Control-Expose-Headers
,Access-Control-Allow-Methods
, orAccess-Control-Allow-Headers
response header, if theAccess-Control-Allow-Credentials
request header is set totrue
.https://fetch.spec.whatwg.org/#cors-protocol-and-credentials
https://fetch.spec.whatwg.org/#http-new-header-syntax
Right now, this module allows it. In fact, it does it by default if the
credentials
option is set totrue
.Instead, it could either:
Origin
request header, if specified. TheVary: Origin
response header would need to be set too then.The text was updated successfully, but these errors were encountered: