php sec-websocket-accept,http – 从“Sec-WebSocket-Key”生成“Sec-WebSocket-Accept”

印高阳
2023-12-01

我跟随

rfc6455:

Concretely, if as in the example above, the |Sec-WebSocket-Key|

header field had the value “dGhlIHNhbXBsZSBub25jZQ==”, the server

would concatenate the string “258EAFA5-E914-47DA-95CA-C5AB0DC85B11”

to form the string “dGhlIHNhbXBsZSBub25jZQ==258EAFA5-E914-47DA-95CA-

C5AB0DC85B11″. The server would then take the SHA-1 hash of this,

giving the value 0xb3 0x7a 0x4f 0x2c 0xc0 0x62 0x4f 0x16 0x90 0xf6

0x46 0x06 0xcf 0x38 0x59 0x45 0xb2 0xbe 0xc4 0xea. This value is

then base64-encoded (see Section 4 of [RFC4648]), to give the value

“s3pPLMBiTxaQ9kYGzzhZRbK+xOo=”. This value would then be echoed in

the |Sec-WebSocket-Accept| header field.

并且无法生成正确的“Sec-WebSocket-Accept”.

用于“dGhlIHNhbXBsZSBub25jZQ == 258EAFA5-E914-47DA-95CA-C5AB0DC85B11”的online SHA1 hash给出了正确的结果:“b37a4f2cc0624f1690f64606cf385945b2bec4ea”,如rfc6455中所述.

但是对于输入“b37a4f2cc0624f1690f64606cf385945b2bec4ea”,online Base64 Encode给出了错误的结果“YjM3YTRmMmNjMDYyNGYxNjkwZjY0NjA2Y2YzODU5NDViMmJlYzRlYQ ==”.

结果应为“s3pPLMBiTxaQ9kYGzzhZRbK xOo =”

我究竟做错了什么?

 类似资料: