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

WS Server using Safari: Status Code 400 #13

Closed
jrstanley opened this issue Jan 16, 2012 · 3 comments
Closed

WS Server using Safari: Status Code 400 #13

jrstanley opened this issue Jan 16, 2012 · 3 comments

Comments

@jrstanley
Copy link

I am trying to connect to a WebSocketServer. Using Chrome this works fine, but using Safari I am getting an error saying a status code 400 is returned. I believe this might be something to do with the protocol versions, does this library support detecting and using the appropriate protocol for browsers?

Thanks
James

@einaros
Copy link
Contributor

einaros commented Jan 16, 2012

Which version of Safari are you using?

On Mon, Jan 16, 2012 at 12:19 PM, jrstanley <
reply@reply.github.com

wrote:

I am trying to connect to a WebSocketServer. Using Chrome this works fine,
but using Safari I am getting an error saying a status code 400 is
returned. I believe this might be something to do with the protocol
versions, does this library support detecting and using the appropriate
protocol for browsers?

Thanks
James


Reply to this email directly or view it on GitHub:
#13

@jrstanley
Copy link
Author

I have tried using Safari 4.1.3 and 5.1.2 on Mac OS X

@einaros
Copy link
Contributor

einaros commented Jan 16, 2012

Right. Looking at http://en.wikipedia.org/wiki/WebSocket#Browser_support, it seems Safari is still lagging behind, and only support the horribly outdated hixie drafts.

ws won't be supporting hixie, as that specification really just has to die.

websocket.io, on the other hand, which falls back to using ws' fast parsers for updated protocols, does support hixie. I suggest you try that :)

@einaros einaros closed this as completed Jan 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants