Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Same origin stops working for WebSocket/SockJS once any origin is configured [SPR-13464] #18044

Closed
spring-projects-issues opened this issue Sep 13, 2015 · 0 comments
Closed

Same origin stops working for WebSocket/SockJS once any origin is configured [SPR-13464] #18044

spring-projects-issues opened this issue Sep 13, 2015 · 0 comments
Assignees
@sdeleuze
Labels
type: enhancement
Milestone
4.2.2

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Sep 13, 2015

Rossen Stoyanchev opened SPR-13464 and commented

In absence of CORS configuration, WebSocket/SockJS allows same origin. Once an origin is added, same origin stops working (e.g. breaks in Chrome which sends an Origin header even even for same origin).

This doesn't seem intuitive. On the MVC side we seem to have chosen to allow same origin regardless, which makes more sense.

Let's consider this for 4.2.2.

Affects: 4.2.1

Referenced from: commits 299b776
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdeleuze sdeleuze

Labels
type: enhancement
Projects
None yet
Milestone
4.2.2
Development

No branches or pull requests
2 participants
@sdeleuze @spring-projects-issues