search

yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

WebSocket Draft 76 Sec-WebSocket-Key Handling does not work in Netty #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The currently used Netty libary netty-3.2.0.ALPHA4.jar apparently does not yet 
support the Sec-WebSocket-Key introduced with latest draft 76 as described 
here: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-76. 

You can test it with the Chrome Frame 5 for IE which was released mid of June. 
For sure the Chrome Browser and the others will catch up soon.

2010-06-18 13:26:16,498 DEBUG - NettyEngineHandler: message received in the 
engine handler
2010-06-18 13:26:16,500 DEBUG - NettyConnector: Starting Netty connector...
2010-06-18 13:26:16,501 INFO  - NettyConnector: Started Netty connector on 
port55397.
2010-06-18 13:26:16,501 DEBUG - NettyEngine: Detected new connector at port 
55397.
2010-06-18 13:26:16,502 DEBUG - TokenServer: Processing connector '55397' 
started...
2010-06-18 13:26:16,503 DEBUG - BasePlugInChain: Notifying plug-ins that 
connector started...
2010-06-18 13:26:16,505 DEBUG - SystemPlugIn: Sending welcome...
2010-06-18 13:26:16,506 DEBUG - SystemFilter: Checking outgoing token from [not 
given] to 55397: 
{vendor=jWebSocket.org,type=welcome,timeout=120000,sourceId=55397,usid=32fc81870
87340b4effe8725e05eb110,version=0.9.0.0618 beta}...
2010-06-18 13:26:16,507 DEBUG - TokenServer: Sending token 
'{vendor=jWebSocket.org,type=welcome,timeout=120000,sourceId=55397,usid=32fc8187
087340b4effe8725e05eb110,version=0.9.0.0618 beta}' to '127.0.0.1:55397'...
2010-06-18 13:26:16,508 DEBUG - SystemPlugIn: Broadcasting connect...
2010-06-18 13:26:16,509 DEBUG - TokenServer: Broadcasting token 
'{name=connect,clientCount=1,type=event,sourceId=55397} to all token based 
connectors...
2010-06-18 13:26:16,510 DEBUG - SystemFilter: Checking outgoing token from 
55397 to [not given]: {name=connect,clientCount=1,type=event,sourceId=55397}...
2010-06-18 13:26:16,511 DEBUG - CustomServer: Processing connector started...
2010-06-18 13:26:16,511 DEBUG - BasePlugInChain: Notifying plug-ins that 
connector started...
2010-06-18 13:26:16,512 DEBUG - NettyEngineHandler: Channel is disconnected:An 
established connection was aborted by the software in your host machine
2010-06-18 13:26:16,513 DEBUG - NettyEngineHandler: Channel is disconnected
2010-06-18 13:26:16,514 DEBUG - NettyEngine: Detected stopped connector at port 
55397.
2010-06-18 13:26:16,514 DEBUG - TokenServer: Processing connector '55397' 
stopped...
2010-06-18 13:26:16,515 DEBUG - BasePlugInChain: Notifying plug-ins that 
connector stopped (CLIENT)...
2010-06-18 13:26:16,516 DEBUG - SystemPlugIn: Broadcasting disconnect...
2010-06-18 13:26:16,516 DEBUG - TokenServer: Broadcasting token 
'{name=disconnect,clientCount=1,type=event,sourceId=55397} to all token based 
connectors...
2010-06-18 13:26:16,517 DEBUG - SystemFilter: Checking outgoing token from 
55397 to [not given]: 
{name=disconnect,clientCount=1,type=event,sourceId=55397}...
2010-06-18 13:26:16,518 DEBUG - CustomServer: Processing connector stopped...
2010-06-18 13:26:16,518 DEBUG - BasePlugInChain: Notifying plug-ins that 
connector stopped (CLIENT)...

Original issue reported on code.google.com by fivefeetfurther@gmail.com on 18 Jun 2010 at 11:34

GoogleCodeExporter commented 8 years ago 
For spec also see:
http://en.wikipedia.org/wiki/Web_socket

Original comment by fivefeetfurther@gmail.com on 18 Jun 2010 at 11:48

GoogleCodeExporter commented 8 years ago 
This is fixed now. we can close this

Original comment by mailtopu...@gmail.com on 28 Jun 2010 at 4:42