Skip to content

Services providing allowedOrigins may make Gateway fail #4858

Description

@pablocarle

Describe the bug

Original conversation: #4718 (comment)

with corsEnabled true in Gateway, there is nothing to prevent an error in Gateway if a service provides * as allowedOrigin.

It's relatively low risk since it's not recommended to set *, but Gateway under this scenario uses allowedOrigin instead of allowedOriginPattern.

Expected behavior
If the service provides * it should use allowedOriginPattern.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status
    Unplanned Bugs

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions