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)

Why not instead have the spec instead require caching of the result of the HTTP-redirect fetch?

It’s not clear at all to me what value there would be for a UA to cache the 30x redirect responses themselves, if the UA is every time just going to load the 30x and then right away make a new request for the resource/response it redirects to?

I mean, I realize the UA will (should) likely also have a cached response for the resource the 30x redirects to. But the required spec behavior still results in an additional request being made, for every 30x redirect, every time.

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

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