| Index: third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt b/third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..eb401c6f61306927427aa6a69fd048f29d32bfeb
|
| --- /dev/null
|
| +++ b/third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
|
| @@ -0,0 +1,11 @@
|
| +CONSOLE WARNING: Found a header value that doesn't match the field-content token production (containing invalid octets. see RFC 7230). We are experimenting whether we can throw for such header values (see: https://www.chromestatus.com/feature/6457425448140800).
|
| +XMLHttpRequest.setRequestHeader() with control octets rejected by RFC 7230 should show a deprecation message.
|
| +
|
| +On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
|
| +
|
| +
|
| +PASS xhr.responseText.match(/HTTP_TEST1: a\x01b\r?\n/) is not null
|
| +PASS successfullyParsed is true
|
| +
|
| +TEST COMPLETE
|
| +
|
|
|