Closed Bug 1539632 Opened 8 months ago Closed 8 months ago

[wpt-sync] Sync PR 16036 - Verify `Sec-Fetch-Site` is correct for domains with trailing dots.

Categories

(Core :: DOM: Core & HTML, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Mike West <mkwst@chromium.org> wrote:

Verify Sec-Fetch-Site is correct for domains with trailing dots.

example.com != example.com.. These are clearly distinct origins,
and we don't currently consider them to have the same registrable
domain (though there's a bit of a question about that. See
https://github.com/publicsuffix/list/issues/792), so they ought
to compare as cross-site

This patch adds a test for this behavior, and teaches the test harness
to resolve domains that end in .test..

Closes https://github.com/mikewest/sec-metadata/issues/15.

Bug: 843478
Change-Id: Ic71afeda69f274c23c19608177756d882307a59d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1536180
Commit-Queue: Mike West \<mkwst@chromium.org>
Reviewed-by: Łukasz Anforowicz \<lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#644261}

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0a934b7e89ef
[wpt PR 16036] - Verify `Sec-Fetch-Site` is correct for domains with trailing dots., a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6ca0a07819ae
[wpt PR 16036] - Verify `Sec-Fetch-Site` is correct for domains with trailing dots., a=testonly
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.