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

Also been meaning to ask for a while now but didn't know the place as the context is spread between WHATWG & W3C and all places in between.

Regards to preloading (therefore fetch) I do realize [there is a bug in chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=593267) for `link as=document` not working. I noticed `as=script` and `as=fetch` all use `*/*`. However `as=font` and `as=style` send `Accept` similar to browser defaults. would `document` send the default UA `Accept: text/html,...,*/*;q=0.9` or `*/*`? I think it should be the former of the two.

This has been a concern for me in keeping MDN docs up to date as am noticing [documentation is already starting to send out (potentially) incorrect information](https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content#The_basics)

> preload has other advantages too. Using as to specify the type of content to be preloaded allows the browser to:
>> Prioritize resource loading more accurately.
>> Match future requests, reusing the same resource if appropriate.
>> Apply the correct content security policy to the resource.
>> **Set the correct Accept request headers for it.**

_"correct"_ is the word that concerns me and who defines it.

Please forgive me if this is a vendor specific topic similar to `as=document` but I feel some vendor specific topics we can aid a touch with proactive avoidance within the spec.

Thanks in advance to whoever has information! I feel this is a relative place to ask.  Has been a mystery to me for months since the feature is broken at the vendor.

-- 
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-373426508