Closed Bug 1557344 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16833 - Hide Sec-Fetch-... headers from service worker `fetch` event.

Categories

(Core :: DOM: Networking, defect, P4)

Product:
Core
Component:
DOM: Networking
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla69
Tracking Flags:
Tracking Status
firefox69 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync upstream][necko-triaged] )

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

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

Lukasz Anforowicz <lukasza@chromium.org> wrote:

Hide Sec-Fetch-... headers from service worker fetch event.

This CL excludes Sec-Fetch-... request headers from the Request object
passes to the service worker's fetch event. This CL also adds WPT
tests that verify that these request headers will be re-added when the
service worker forwards the request back into the network (via implicit
fallback, or via an explicit responseWith+fetch).

Bug: 949997
Change-Id: I04422a1630f62b497961ca1789007f2402148e76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611314
Commit-Queue: Łukasz Anforowicz \<lukasza@chromium.org>
Reviewed-by: Matt Falkenhagen \<falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#659937}

Component: web-platform-tests → DOM: Networking
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][necko-triaged]
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f2d93f4dd84a
[wpt PR 16833] - Hide Sec-Fetch-... headers from service worker `fetch` event., a=testonly

https://hg.mozilla.org/mozilla-central/rev/f2d93f4dd84a

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [wptsync downstream][necko-triaged] → [wptsync upstream][necko-triaged]
You need to log in before you can comment on or make changes to this bug.