tree fc8b2c5e4df371af23b03a0e32b9b02d4260a10e
parent a83bf9a725f275854b37d31dc1708d08c5dd5670
author Ryo Ogawa <negibokken@gmail.com> 1701711444 -0800
committer Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> 1701712439 -0800

Fix handling invalid date for Expires header value "0" as expired

This CL changes handling the invalid Expires header value "0" as a time in the
past and stale, as described in section 5.3 [1] of RFC 9111.

> 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://www.rfc-editor.org/rfc/rfc9111.html#section-5.3

Bug: 853508
Change-Id: I853b2972c4420936fda8373e292d2d90fdb7988a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4021895
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232768}