Re: [whatwg/fetch] Accept headers in spec cause confusion (#274)

From #877

> This should be adapted to give user agents the possibility to include image formats that might not be universally accepted but preferred, e.g. `image/webp` or `image/apng` or `image/jxr`, and to exclude formats that might not be supported or preferred (e.g. excluding svg support for agents on systems where vector graphics are disproportionately expensive to process), to allow server-driven [conneg](https://en.wikipedia.org/wiki/Content_negotiation) to happen with servers that support multiple other formats.

As it stands, the spec doesn't allow for this kind of required flexibility, since it creates the expectation that all user agent should align, and users agents would not be spec compliant if they indicate their capabilities to servers which is in many situations desired. What's the point of the Accept headers if you're not actually allowed to use them for what they are for?

-- 
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/274#issuecomment-545837311