[WebSocket]Browser must fail connection if Sec-WebSocket-Protocol mismatched.
[WebKit-https.git] / LayoutTests / ChangeLog
index 34b4bc3..1380cc6 100644 (file)
@@ -1,3 +1,23 @@
+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 response includes a |Sec-WebSocket-Protocol| header field
+        and this header field indicates the use of a subprotocol that was
+        not present in the client's handshake (the server has indicated a
+        subprotocol not requested by the client), the client MUST _Fail
+        the WebSocket Connection_.
+
+        * http/tests/websocket/tests/hybi/handshake-fail-by-mismatch-protocol-header-expected.txt: Added.
+        * http/tests/websocket/tests/hybi/handshake-fail-by-mismatch-protocol-header.html: Added.
+        * http/tests/websocket/tests/hybi/handshake-fail-by-mismatch-protocol-header_wsh.py: Added.
+        (web_socket_do_extra_handshake):
+        (web_socket_transfer_data):
+
 2012-03-28  David Grogan  <dgrogan@chromium.org>
 
         IndexedDB: don't expose IDBDatabaseError to script