Closed mateuszdw closed 10 years ago
this issue can be related with commit https://github.com/faye/faye-websocket-ruby/commit/799103fd47a1d061c864e105993c7f513fa39b45
I recently ran across this problem myself and isolated the problem to Cramp's send_initial_response
method. It was erroneously sending additional responses after a WebSocket connection had been negotiated by Faye, thus displaying the errors you were seeing. I have an open PR that appears to fix the problem.
Since cramp is depedent of
'faye-websocket', '~> 0.7.1'
I have problem with websockets connection. Looks like Thin breaking something On latest version websockets response looks like this:Previous dependency
'faye-websocket', '~> 0.4.6'
givesTested with 1.9.3-p392 and Gemfile dependencies
So simple app in cramp does not work in current version