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

Issues Search
    My Issues | Starred     Open | Closed | All

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

Issue 1378543002: Add UMA for header values in XHR's setRequestHeader() checked against RFC 7230 (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Update test expectations due to message change. 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
« third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets.html ('K') | « third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets.html ('k') | third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/normalize-affected-1.html » ('j') | third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/normalize-affected-1.html » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
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..e1cb9d3dc0bf34c023ad4264031d832a235c3e66
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets-expected.txt
@@ -0,0 +1,5 @@
+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).
+This is a testharness.js-based test.
+PASS setRequestHeader() with control octets
+Harness: the test ran to completion.
+
« third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets.html ('K') | « third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/invalid-octets.html ('k') | third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/normalize-affected-1.html » ('j') | third_party/WebKit/LayoutTests/http/tests/xmlhttprequest/header-value-update/normalize-affected-1.html » ('J')

Powered by Google App Engine
This is Rietveld 408576698