Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

joshua__lim
Hi,

I was trying to use Jeff Mesnil's webworker example (https://github.com/jmesnil/stomp-websocket/tree/master/example/webworker) for the STOMP Over WebSocket to connect to RabbitMQ's SOCKJS server but encountered an error:

WebSocket connection to 'ws://localhost:15674/stomp/websocket' failed: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received :8080/stomp.js:374

Line 374 is "ws = new klass(url, protocols);".

I've copied stomp.js to http://pastebin.com/td6nuhSX

Any advice will be much appreciated.

Rgds,
Joshua
Reply | Threaded
Open this post in threaded view
|

Re: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

Michael Klishin-2
On 21 March 2014 at 16:53:47, joshua__lim ([hidden email]) wrote:
> > WebSocket connection to 'ws://localhost:15674/stomp/websocket'  
> failed: Error
> during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol'  
> header
> but no response was received :8080/stomp.js:374
>  
> Line 374 is "ws = new klass(url, protocols);”.

RabbitMQ Web STOMP uses /stomp. Have you seen/tried code examples
on http://www.rabbitmq.com/web-stomp.html
--  
MK  

Software Engineer, Pivotal/RabbitMQ
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Reply | Threaded
Open this post in threaded view
|

RE: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

joshua__lim
Hi Michael,

I've tried ws://localhost:15674/stomp and got a 200 error instead.

ws://localhost:15674/stomp/websocket appears to be correct.

Please see this thread - http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-s-WebSocket-broken-td30408.html

Rgds,
Joshua



Date: Thu, 10 Apr 2014 02:15:07 -0700
From: [hidden email]
To: [hidden email]
Subject: Re: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

On 21 March 2014 at 16:53:47, joshua__lim ([hidden email]) wrote:
> > WebSocket connection to 'ws://localhost:15674/stomp/websocket'  
> failed: Error
> during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol'  
> header
> but no response was received :8080/stomp.js:374
>  
> Line 374 is "ws = new klass(url, protocols);”.

RabbitMQ Web STOMP uses /stomp. Have you seen/tried code examples
on http://www.rabbitmq.com/web-stomp.html
--  
MK  

Software Engineer, Pivotal/RabbitMQ
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss



To unsubscribe from Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

Michael Klishin-2
On 10 April 2014 at 20:03:53, joshua__lim ([hidden email]) wrote:
> > I've tried ws://localhost:15674/stomp and got a 200 error  
> instead.
>  
> ws://localhost:15674/stomp/websocket appears to be correct.  

OK, so it’s likely a hole in our implementation:

https://tools.ietf.org/html/rfc6455#section-11.3.4 
--  
MK  

Software Engineer, Pivotal/RabbitMQ
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

Michael Klishin-2
On 14 April 2014 at 16:14:22, Michael Klishin ([hidden email]) wrote:
> > OK, so it’s likely a hole in our implementation:
>  
> https://tools.ietf.org/html/rfc6455#section-11.3.4

This should be fixed in 3.3.0. Can you try that version
and let us know how it goes? 
--  
MK  

Software Engineer, Pivotal/RabbitMQ
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss