Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(538)

Side by Side Diff: LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

Issue 101143002: Remove hybi sub directory for WebSocket layout tests (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Created 7 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=126_125' failed: The minimal number of bytes MUST be used to enc ode the length 1 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=126_125' failed: The minimal number of bytes MUST be used to enc ode the length
2 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=126_0' failed: The minimal number of bytes MUST be used to encod e the length 2 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=126_0' failed: The minimal number of bytes MUST be used to encod e the length
3 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=127_65535' failed: The minimal number of bytes MUST be used to e ncode the length 3 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=127_65535' failed: The minimal number of bytes MUST be used to e ncode the length
4 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=127_0' failed: The minimal number of bytes MUST be used to encod e the length 4 CONSOLE ERROR: line 21: WebSocket connection to 'ws://127.0.0.1:8880/invalid-enc ode-length?case=127_0' failed: The minimal number of bytes MUST be used to encod e the length
5 Test whether WebSocket aborts the connection when it receives an unexpected enco ding length frame. 5 Test whether WebSocket aborts the connection when it receives an unexpected enco ding length frame.
6 6
7 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ". 7 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".
8 8
9 Case 126_125: Test started. 9 Case 126_125: Test started.
10 onopen() was called. 10 onopen() was called.
11 onclose() was called. 11 onclose() was called.
12 PASS closeEvent.wasClean is false 12 PASS closeEvent.wasClean is false
13 Case 126_0: Test started. 13 Case 126_0: Test started.
14 onopen() was called. 14 onopen() was called.
15 onclose() was called. 15 onclose() was called.
16 PASS closeEvent.wasClean is false 16 PASS closeEvent.wasClean is false
17 Case 127_65535: Test started. 17 Case 127_65535: Test started.
18 onopen() was called. 18 onopen() was called.
19 onclose() was called. 19 onclose() was called.
20 PASS closeEvent.wasClean is false 20 PASS closeEvent.wasClean is false
21 Case 127_0: Test started. 21 Case 127_0: Test started.
22 onopen() was called. 22 onopen() was called.
23 onclose() was called. 23 onclose() was called.
24 PASS closeEvent.wasClean is false 24 PASS closeEvent.wasClean is false
25 PASS successfullyParsed is true 25 PASS successfullyParsed is true
26 26
27 TEST COMPLETE 27 TEST COMPLETE
28 28
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698