Skip to content

Bug: providing multiple comma-separated CORS origins fails #9063

@rnza0u

Description

@rnza0u

I am using AWS::Serverless::Api.

Providing multiple origins through the Cors.AllowOrigin property results in an invalid Access-Control-Allow-Origin header being received by the browser.

The documentation suggests that multiple origins are supported : https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-property-api-corsconfiguration.html

When i have the following in my template :

AllowOrigin: "'http://origin-1,http://origin-2'"

The server returns :

Access-Control-Allow-Origin: http://origin-1,http://origin-2

Which is invalid according to the CORS specification.

SAM needs to return only one origin in the Access-Control-Allow-Origin header, namely the one that matches the Origin request header.

Metadata

Metadata

Assignees

No one assigned

    Labels

    stage/needs-triageAutomatically applied to new issues and PRs, indicating they haven't been looked at.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions