[WebSocket]Browser must fail connection if Sec-WebSocket-Protocol mismatched.
[WebKit-https.git] / Source / WebCore / ChangeLog
index 5b2eaab..1475a4a 100644 (file)
@@ -1,3 +1,19 @@
+2012-03-28  Li Yin  <li.yin@intel.com>
+
+        [WebSocket]Browser must fail connection if Sec-WebSocket-Protocol mismatched.
+        https://bugs.webkit.org/show_bug.cgi?id=82307
+
+        Reviewed by Kent Tamura.
+
+        From RFC6455: http://tools.ietf.org/html/rfc6455#section-4.1
+        If the WebSocket openhanding respond included the mismatched
+        Sec-WebSocket-Protocol header field, the client must fail the WebSocket Connection.
+
+        Test: http/tests/websocket/tests/hybi/handshake-fail-by-mismatch-protocol-header.html
+
+        * Modules/websockets/WebSocketHandshake.cpp:
+        (WebCore::WebSocketHandshake::checkResponseHeaders):
+
 2012-03-28  Jessie Berlin  <jberlin@apple.com>
 
         Fix Windows build after r112482.