Closed Bug 1860379 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42675 - Fix Expires method of resource to treat invalid date string as expired

Categories

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

task

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

bokken <negibokken@gmail.com> wrote:

Fix Expires method of resource to treat invalid date string as expired

This CL fixes to make the Expires() method treat invalid date formats as
a time in the past, as described in section 5.3 of RFC 9111 [1].

A cache recipient MUST interpret invalid date formats, especially the
value "0", as representing a time in the past (i.e., "already
expired").

[1] https://httpwg.org/specs/rfc9111.html#rfc.section.5.3

Bug: 853508
Change-Id: I853b2972c4420936fda8373e292d2d90fdb7988a
Reviewed-on: https://chromium-review.googlesource.com/4021895
WPT-Export-Revision: 36231c9f5fc8ae12e3ca42d35d0617223c869588

Component: web-platform-tests → DOM: Networking
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 4 tests and 17 subtests

Status Summary

Firefox

OK : 4
PASS: 68

Chrome

OK : 4
PASS: 64
FAIL: 4

Safari

OK : 4
PASS: 44
FAIL: 24

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/98742a9162d5 [wpt PR 42675] - Fix handling invalid date for Expires header value "0" as expired, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.