Re: [whatwg/fetch] Editorial: Use controller for navigation redirect (PR #1469)

> The existing setup is indeed broken. I'm wondering what our long(er) term perspective is here. I'm also worried that if we keep using the same fetch, fetch controller, and fetch params, we'll end up with weird timing and state situations on them. Typically when you've seen "process response" you wouldn't expect to start uploading again, for instance.

The long term perspective is that this is a single navigation fetch, that gets its redirects followed manually rather than automatically. So it makes sense that it shares the same fetch params and state. This is equivalent to how the chromium implementation works - there's a "follow" function that's specific to navigations rather than a whole new fetch.
Does HTML upload data in the middle of a navigation redirect chain? Otherwise I don't see how the example applies.

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

Message ID: <whatwg/fetch/pull/1469/c1258265140@github.com>