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

Unified Diff: LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt

Issue 1342443004: [MIGRATED] Make deprecation warnings on XHR's setRequestHeader more accurate (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@temp1288263003
Patch Set: Reflect tyoshino's comments. Created 5 years, 3 months 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 side-by-side diff with in-line comments
Download patch
Index: LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
diff --git a/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt b/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..e1608817fda0962c1d9fba4132ff38aec36a9b58
--- /dev/null
+++ b/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
@@ -0,0 +1,5 @@
+CONSOLE WARNING: Header values not matching to RFC 7230 (containing invalid octets). We are experimenting whether such header values can be deprecated (see: https://www.chromestatus.com/feature/6457425448140800).
+This is a testharness.js-based test.
+PASS setRequestHeader() with control octets
+Harness: the test ran to completion.
+

Powered by Google App Engine
This is Rietveld 408576698