Re: [fetch] RequestCache "reload" type must also set no-cache headers (#201)

Hmm, good question.

>From one perspective, in case the developer has not included `no-cache` then they're probably doing the wrong thing (unless if they can somehow guarantee that there will never be an HTTP cache along the way!).

But more importantly, they might have set the header as `Cache-Control: no-cache no-store` or some such.  So I guess we should only set these headers if the developer has not set them...

(FWIW this is already how Gecko behaves for things such as XHR, if my reading of the code is correct.)

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/201#issuecomment-174806572