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 flag AddDefaultAuthorizerToCorsPreflight skips Authorizers for preflight methods, however, it does not skip the requirement of an API-Key (as far as the UsagePlan is linked to a key). Browsers do never add the X-API-Key Header to the preflight request.
At the moment I have no idea how to omit ApiKey requirement for the preflight requests other than switching them off in the console after each deploy. Pls give me a hint if it can be stated in the template somehow. Thanks.
Proposal
Either generally disable ApiKey Requirement for Preflight requests, or add a flag similar to AddDefaultAuthorizerToCorsPreflight, named something like ApiKeyRequiredToCorsPreflight.
Describe your idea/feature/enhancement
The flag
AddDefaultAuthorizerToCorsPreflight
skips Authorizers for preflight methods, however, it does not skip the requirement of an API-Key (as far as theUsagePlan
is linked to a key). Browsers do never add theX-API-Key
Header to the preflight request.At the moment I have no idea how to omit ApiKey requirement for the preflight requests other than switching them off in the console after each deploy. Pls give me a hint if it can be stated in the template somehow. Thanks.
Proposal
Either generally disable ApiKey Requirement for Preflight requests, or add a flag similar to
AddDefaultAuthorizerToCorsPreflight
, named something likeApiKeyRequiredToCorsPreflight
.Things to consider:
Yes
Additional Details
The text was updated successfully, but these errors were encountered: