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

Non-binary websocket messages #137

Open

dbrgn opened this issue Nov 13, 2017 · 1 comment

Assignees

Member

dbrgn commented Nov 13, 2017

What should we do when non-binary websocket messages arrive?

Right now I think they're simply dropped in all implementations. But maybe we should raise a ProtocolError instead?

Does the spec already say something about this case?

dbrgn assigned lgrahl

Member

lgrahl commented Nov 13, 2017

I don't think it does specify what needs to happen. Sure, as always, let's raise ProtocolError in such a case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment