Closed Bug 1518435 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 14747 - SignedExchange: Verify if the response is cacheable by a shared cache

Categories

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

enhancement

Tracking

(firefox67 fixed)

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Kunihiko Sakamoto <ksakamoto@chromium.org> wrote:

SignedExchange: Verify if the response is cacheable by a shared cache

This implements the step 6 of [1]. Signed exchange is not valid if
response is not cacheable by a shared cache.

[1] https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#cross-origin-trust

Bug: 919414
Change-Id: I2ceef3c0e3899ae1b9bbe1e0bb644b601732cbe0
Reviewed-on: https://chromium-review.googlesource.com/1400422
WPT-Export-Revision: ac1c960144dae8b44449b3d001ed4a238257fe15

PR 14747 applied with additional changes from upstream: 2e19cbe5d5d74821056d4ae2cef435accefaf4ef, e663fa084dcdac43fea5cdd6c69b059b5ad0743f
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a68637e80a82
[wpt PR 14747] - SignedExchange: Verify if the response is cacheable by a shared cache, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/8e1019eda748
[wpt PR 14747] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6e83379f4407
[wpt PR 14747] - SignedExchange: Verify if the response is cacheable by a shared cache, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/b79cff27bb8e
[wpt PR 14747] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.