WebSocket header continuations test case.

net/websockets/websocket_end_to_end_test.cc

Index: net/websockets/websocket_end_to_end_test.cc
diff --git a/net/websockets/websocket_end_to_end_test.cc b/net/websockets/websocket_end_to_end_test.cc
index 2fbc20b6ae65f7a984412a22482aa1f2f2aa9e76..e652fe05408f6baef7eb81ea029219dee1ff01e4 100644
--- a/net/websockets/websocket_end_to_end_test.cc
+++ b/net/websockets/websocket_end_to_end_test.cc
@@ -470,6 +470,24 @@ TEST_F(WebSocketEndToEndTest, DISABLED_ON_ANDROID(TrailingWhitespace)) {
   EXPECT_EQ("sip", event_interface_->selected_subprotocol());
 }
 
+// This is a regression test for crbug.com/169448 "WebSockets should support
+// header continuations"
+// TODO(ricea): HTTP continuation headers have been deprecated by RFC7230.  If
+// support for continuation headers is removed from Chrome, then this test will
+// break and should be removed.
+TEST_F(WebSocketEndToEndTest, DISABLED_ON_ANDROID(HeaderContinuations)) {
+  SpawnedTestServer ws_server(SpawnedTestServer::TYPE_WS,
+                              SpawnedTestServer::kLocalhost,
+                              GetWebSocketTestDataDirectory());
+  ASSERT_TRUE(ws_server.Start());
+
+  GURL ws_url = ws_server.GetURL("header-continuation");
+
+  EXPECT_TRUE(ConnectAndWait(ws_url));
+  EXPECT_EQ("permessage-deflate; server_max_window_bits=10",
+            event_interface_->extensions());
+}
+
 }  // namespace
 
 }  // namespace net