Re: [whatwg/fetch] Refreshing of stale response assumed to always be successful (#950)

> HTTP doesn't specify it because it's pretty generic, but I could see Fetch doing so (if you can get everyone to agree).

Ok thanks for clarifying, so then Fetch is indeed the right place to handle this(opposite of what I suggested earlier). 

> Whether or not the client retries the request is up to it -- but usually it will

Just to clarify "retrying" in this context, would it mean sending the initial request, but stripped of any re-validation headers(essentially switching to a "normal" request for the full resource)? 
This is sort of what I tried to sketch over at https://github.com/whatwg/fetch/pull/1041

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