2011-12-18 117 views
1

我想实现最新的websocket规范。但是,我无法通过成功握手后的揭密步骤。websocket客户端数据包unframe/unmask

我收到以下web套接字帧:

<<129,254,1,120,37,93,40,60,25,63,71,88,92,125,80,81,73, 
51,91,1,2,53,92,72,85,103,7,19,79,60,74,94,64,47,6,83, 
87,58,7,76,87,50,92,83,70,50,68,19,77,41,92,76,71,52, 
70,88,2,125,90,85,65,96,15,14,20,107,31,14,28,100,27,9, 
17,122,8,72,74,96,15,86,68,37,68,18,76,48,15,28,93,48, 
68,6,73,60,70,91,24,122,77,82,2,125,80,81,85,45,18,74, 
64,47,91,85,74,51,21,27,20,115,24,27,5,37,69,80,75,46, 
18,68,72,45,88,1,2,40,90,82,31,37,69,76,85,103,80,94, 
74,46,64,27,5,60,75,87,24,122,25,27,5,47,71,73,81,56, 
21,27,93,48,88,76,31,57,77,74,11,55,73,68,73,115,65,81, 
31,104,26,14,23,122,8,75,68,52,92,1,2,110,24,27,5,53, 
71,80,65,96,15,13,2,125,75,83,75,41,77,82,81,96,15,72, 
64,37,92,19,93,48,68,7,5,62,64,93,87,46,77,72,24,40,92, 
90,8,101,15,28,83,56,90,1,2,108,6,13,21,122,8,82,64,42, 
67,89,92,96,15,93,19,56,28,8,65,101,31,94,16,105,28,10, 
20,56,30,14,65,56,27,93,71,106,16,11,17,63,25,4,17,57, 
73,89,17,59,29,88,29,106,24,27,5,46,65,72,64,54,77,69, 
24,122,66,93,93,49,5,12,8,109,15,28,76,59,90,93,72,56, 
76,1,2,41,90,73,64,122,8,89,85,50,75,84,24,122,25,15, 
23,105,25,5,19,106,26,14,20,111,25,27,5,53,77,85,66,53, 
92,1,2,110,26,13,2,125,95,85,65,41,64,1,2,108,27,10,19, 
122,7,2>> 

作为每这里定义的基成帧协议(http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-17#section- 5.2)我有:

fin:1, rsv:0, opcode:1, mask:1, length:126 

屏蔽应用+有效载荷数据出来是:

<<87,58,7,76,87,50,92,83,70,50,68,19,77,41,92,76,71,52,70,88,2,125,90,85,65,96, 
15,14,20,107,31,14,28,100,27,9,17,122,8,72,74,96,15,86,68,37,68,18,76,48,15, 
28,93,48,68,6,73,60,70,91,24,122,77,82,2,125,80,81,85,45,18,74,64,47,91,85, 
74,51,21,27,20,115,24,27,5,37,69,80,75,46,18,68,72,45,88,1,2,40,90,82,31,37, 
69,76,85,103,80,94,74,46,64,27,5,60,75,87,24,122,25,27,5,47,71,73,81,56,21, 
27,93,48,88,76,31,57,77,74,11,55,73,68,73,115,65,81,31,104,26,14,23,122,8,75, 
68,52,92,1,2,110,24,27,5,53,71,80,65,96,15,13,2,125,75,83,75,41,77,82,81,96, 
15,72,64,37,92,19,93,48,68,7,5,62,64,93,87,46,77,72,24,40,92,90,8,101,15,28, 
83,56,90,1,2,108,6,13,21,122,8,82,64,42,67,89,92,96,15,93,19,56,28,8,65,101, 
31,94,16,105,28,10,20,56,30,14,65,56,27,93,71,106,16,11,17,63,25,4,17,57,73, 
89,17,59,29,88,29,106,24,27,5,46,65,72,64,54,77,69,24,122,66,93,93,49,5,12,8, 
109,15,28,76,59,90,93,72,56,76,1,2,41,90,73,64,122,8,89,85,50,75,84,24,122, 
25,15,23,105,25,5,19,106,26,14,20,111,25,27,5,53,77,85,66,53,92,1,2,110,26, 
13,2,125,95,85,65,41,64,1,2,108,27,10,19,122,7,2>> 

尽管32位掩码荷兰国际集团关键是:

<<37,93,40,60,25,63,71,88,92,125,80,81,73,51,91,1,2,53,92,72,85,103,7,19,79,60, 
74,94,64,47,6,83>> 

http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-17#section-5.2

j     = i MOD 4 
transformed-octet-i = original-octet-i XOR masking-key-octet-j 

不过,我似乎并没有让我从客户端,这基本上是一个XML包发送原始字节的。任何方向,更正,建议非常感谢。

+0

确实,但是我没有看到基本组帧协议的任何改变。它与上面链接中的定义相同。 – 2011-12-18 12:43:56

+0

查看github上的misultin项目。它有你需要的所有websocket解析代码。原始代码使用基于过程的方法,并且重用该代码有点困难(https://github.com/ostinelli/misultin/blob/master/src/misultin_websocket.erl)。如果你需要一个功能类似foldl的解析代码而不是基于进程,请看看我的分歧(https://github.com/gleber/misultin/branches/functionalize-ws-code)。 – gleber 2011-12-19 09:31:09

回答

1

我认为你误读了协议规范的数据组帧部分。

您对第一个字节(129)的解释是正确的 - fin + opcode 1 - 文本消息的最后(和第一)片段。
下一个字节(254)意味着消息的主体被屏蔽,并且接下来的2个字节提供了它的长度(126或127的长度意味着更长的消息,其长度不能用7位表示,126表示以下2个字节保存长度; 127表示其后4个字节)。
以下2个字节 - 1,120--表示消息长度为376字节。
以下4个字节 - 37,93,40,60 - 是你的面具。
其余的数据是你的消息,你写的应该进行改造,使消息

& ltbody的xmlns = 'HTTP://jabber.org/protocol/httpbind' RID = '2167299354' 为='jaxl。 im'xml:lang ='en'xmpp:version ='1.0'xmlns:xmpp ='urn:xmpp:xbosh'ack ='1'route ='xmpp:dev.jaxl.im:5222'wait = '30' hold ='1'content ='text/xml; charset = utf-8'ver ='1.1 0'newkey ='a6e44d87b54461e62de3ab7874b184dae4f5d870'sitekey ='jaxl-0-0'iframed ='true'epoch ='1324196722121'height ='321'width ='1366'/>

+0

还没有尝试过,但我相信这是抓住。可能我确实理解它是正确的,但没有正确实现它(主要是由于在我的erlang代码中不正确处理bit/binary)。谢谢你的正确指针,是的,这确实是我揭露之后寻找的包:)将从这里剔除其余的,谢谢 – 2011-12-20 01:10:16