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.

Sign up for GitHub

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

Test what browsers do when a server replies multiple Sec-WebSocket-Protocol headers #23

Open
nox opened this issue Mar 24, 2017 · 0 comments
Open

Test what browsers do when a server replies multiple Sec-WebSocket-Protocol headers #23

nox opened this issue Mar 24, 2017 · 0 comments
Labels
topic: websockets

Comments

@nox
Copy link
Member

nox commented Mar 24, 2017

"The |Sec-WebSocket-Protocol| header field MUST NOT appear more than once in an HTTP response."
@KiChjang KiChjang mentioned this issue Mar 24, 2017
Merged
@annevk annevk mentioned this issue Jan 30, 2021
Open
@annevk annevk changed the title WebSocket: test what browsers do when a server replies multiple Sec-WebSocket-Protocol headers Test what browsers do when a server replies multiple Sec-WebSocket-Protocol headers Feb 22, 2022
@annevk annevk transferred this issue from whatwg/fetch Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: websockets
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nox @annevk