LayoutTests/http/tests/websocket/long-invalid-header-expected.txt - Issue 101143002: Remove hybi sub directory for WebSocket layout tests

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: LayoutTests/http/tests/websocket/long-invalid-header-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

OLD	NEW
1 CONSOLE ERROR: line 19: WebSocket connection to 'ws://127.0.0.1:8880/long-invali d-header' failed: Unexpected CR in name at ppppppppppppppppppppppppppppppppppppp pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp ppppppppppp…	1 CONSOLE ERROR: line 19: WebSocket connection to 'ws://127.0.0.1:8880/long-invali d-header' failed: Unexpected CR in name at ppppppppppppppppppppppppppppppppppppp pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp ppppppppppp…

2 Make sure WebSocket gives errors on long invalid upgrade header.	2 Make sure WebSocket gives errors on long invalid upgrade header.

3	3

4 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".	4 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE ".

5	5

6 WebSocket is closed	6 WebSocket is closed

7 PASS successfullyParsed is true	7 PASS successfullyParsed is true

8	8

9 TEST COMPLETE	9 TEST COMPLETE

10	10

OLD	NEW