cache-control erroneous request

[gagan-bhullar-tech]

Description

Motivation

PR fixes #35169

Additional details

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Web/HTTP/Headers/Cache-Control

External URLs (1)

URL: /en-US/docs/Web/HTTP/Headers/Cache-Control
Title: Cache-Control

• https://httpwg.org/specs/rfc9111.html (2 times) (Note! This may be a new URL 👀)

(comment last updated: 2024-07-29 02:20:21)

[hamishwillee]

Thank you.

For both requests and responses we know that negative/non-integer max-age values are unspecified/undefined. For responses we know that caches are encouraged to treat the value as 0, but we don't know what requests are expected to do.

I think we can assume that this is true for both requests and responses though, but as you have done here, we can't point to the freshness information in the spec as support for this assertion.

So IMO this is a good fix (with slightly tidied English).

But I think that the original information is also relevant for the responses - it is still (and more) true there. So perhaps we should also copy this removed text into the response directive section?

. I've slightly tidied the English.

The text is correct for responses, so how about we copy it up to the response senction?

[gagan-bhullar-tech]

That makes sense. Added the text to responses section.

[hamishwillee]

Thanks very much @gagan-bhullar-tech !