Skip to content

Allow custom Origins when upgrading to WebSocket transport #1452

@bclozel

Description

@bclozel

Spring Framework provides lots of options to allow custom Origin when upgrading HTTP to WebSocket. We should provide a similar arrangement in Spring for GraphQL.
Let's consider this as a bug of omission and backport the feature in 1.4.x as well.

Metadata

Metadata

Assignees

Labels

in: webIssues related to web handlingstatus: backportedAn issue that has been backported to maintenance branchestype: bugA general bug

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions