Re: [fetch] Add "must-revalidate" to RequestCache enumeration (#165)

My understanding of the `no-cache` semantics was that the cached response will always be revalidated before being used.  That being said, step 15.3 of HTTP-network-or-cache fetch makes me second guess that, but I'll go ahead and assume that prose needs fixing.

With that, we do need to set the right headers for `no-cache`, but I don't think `must-revalidate` is the right header since AFAIK that header is only meaningful on a response, not a request.  The right request header to send is `max-age=0`.  I have already filed #232 about that.

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