1957619 - Firefox caching resources even if they're missing a max-age param

Status: RESOLVED FIXED

(Core :: Networking, defect, P2)

Description

[Valentin Gosu [:valentin] (he/him)]

In bug 1934586 we found a curious case where Firefox was behaving differently from other browsers.
If the response to a POST request is a redirect to a specific URL,

https://bugzilla.mozilla.org/show_bug.cgi?id=1934586#c3

The problem was that the resource has a Cache-Control: private header, which we return from the cache.
However, according to RFC 9111 - 4.2.1
https://www.rfc-editor.org/rfc/rfc9111.html#name-calculating-freshness-lifet

If it's missing max-age and Expires header, it should be considered stale.

Comment 1

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1957619 - Revalidate cached redirects with no max-age or expires headers r=#necko

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/80ee470262e8
Revalidate cached redirects with no max-age or expires headers  r=necko-reviewers,jesup

Comment 3

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/51799 for changes under testing/web-platform/tests

Comment 4

[Cristina Horotan [:chorotan]]

https://hg.mozilla.org/mozilla-central/rev/80ee470262e8

Comment 5

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot