Re: [whatwg/fetch] Spec unexpectedly requires caching 30x responses themselves — rather than caching the result of running HTTP-redirect fetch to follow the 30x redirects (Issue #1765)

If a 301 or 308 response is given, then the UA are expected to update their stored links to the new URI.

However, I'm very unsure what the phrase _"engaged in authoring content"_ is refering to:

> However, this suggestion is usually ignored unless the user agent is actively editing references (e.g., engaged in authoring content)

Spec: https://httpwg.org/specs/rfc9110.html#status.301
Easier explanation: https://http.dev/301

Are there any reason why the fetch spec and HTTP spec diverge on updating the URI?

Note, that the HTTP spec does not say to update the URI indefinitely. But only according to [Section 4.2.2 - Heuristic Freshness](https://httpwg.org/specs/rfc9111.html#heuristic.freshness).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1765#issuecomment-2285727683
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1765/2285727683@github.com>