Closed Bug 1551011 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16697 - [XHR] Use response tainting to calculate CORS-exposed header-name list

Categories

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

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: [necko-triaged][wptsync downstream])

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

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

Yutaka Hirano <yhirano@chromium.org> wrote:

[XHR] Use response tainting to calculate CORS-exposed header-name list

XHR uses the same-originness of the request origin and the destination
URL to calculate the CORS-exposed header-name list, which leads to
wrong results with redirects. Use response tainting as specced.

Bug: 959390
Change-Id: Iec448dfe7d2b47d00f0f471391eb7918a1fe7bc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598949
Reviewed-by: Takashi Toyoshima \<toyoshim@chromium.org>
Commit-Queue: Yutaka Hirano \<yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657626}

Component: web-platform-tests → DOM: Networking
Product: Testing → Core
Priority: P4 → P5
Whiteboard: [wptsync downstream] → [necko-triaged][wptsync downstream]
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/08010ef776df
[wpt PR 16697] - [XHR] Use response tainting to calculate CORS-exposed header-name list, a=testonly

https://hg.mozilla.org/mozilla-central/rev/08010ef776df

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