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 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?

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.

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

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