Re: [fetch] Initializing context/content specific fetch defaults (#43)

It'd be nice, but I suspect implementations are going to want to do their own thing here, to a degree.

Fetch could give advice about what's appropriate; e.g., sending image/wepb for a HTML fetch doesn't make sense (I get that they're trying to hint to the server that it's OK to send links to webp images in the HTML, but that's not really what accept is for, and other browsers don't do it).

We could also save a few bytes by recommending that they not send */*; it doesn't do anything (especially when it's on its own)`.

Latest and greatest:
  http://httpwg.github.io/specs/rfc7231.html#header.accept

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