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)

I’m going ahead and closing this, because after reading up, I have a better understanding than I did when I filed this — to the point where I would not have ended up raising this to begin with, if I had understand better.

> If I'm understanding correctly what you're suggesting then the request URL would not be updated and a bunch of security checks would not end up happening?

I didn’t understand enough to know that would be a consequence.

> Furthermore, a temporary redirect in particular might also change what it redirects to pretty frequently, more frequently than any final response might change.
> 
> There is probably some further short-circuiting possible for permanent redirects, but it would have to be build on top of what we have today I think as we would still have to update the request URL and things like that. And it's not entirely clear what the pay-off for the specification would be to describe such a mechanism.

Agreed on all those points. I don’t now see any need for a spec change here.

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

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