Closed Bug 1809760 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 37894 - [No-Vary-Search] Add non-ASCII key support to the response header

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox111 fixed)

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 37894 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/37894
Details from upstream follow.

Liviu Tinta <liviutinta@chromium.org> wrote:

[No-Vary-Search] Add non-ASCII key support to the response header

Implementation of "parse a key" algorithm from
https://wicg.github.io/nav-speculation/no-vary-search.html#parsing

"parse a key" algorithm allows the encoding of non-ASCII keys in the
ASCII structured header format.

The non-ASCII key would be represented in a percent encoded format
when specified in the No-Vary-Search header.

Example: No-Vary-Search: params=("%C3%A9+%E6%B0%97")

"%C3%A9+%E6%B0%97" in this example represents the key "é 気".

Bug: 1399848, 1378072, 1378075
Change-Id: I02ca2e4956dd242ee0ec28706707b1903b6c8bea

Reviewed-on: https://chromium-review.googlesource.com/4150191
WPT-Export-Revision: 00c36d1ce41e8bdb89ff67a306fc9c3fb5566e88

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed8f9d44d9e7
[wpt PR 37894] - [No-Vary-Search] Add non-ASCII key support to the response header, a=testonly

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 30 tests and 1 subtests

Status Summary

Firefox

OK : 30
FAIL: 30

Chrome

OK : 30
PASS: 7
FAIL: 23

Safari

OK : 30
FAIL: 30

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.