- From: Richard Michael <notifications@github.com>
- Date: Tue, 13 Mar 2018 21:16:39 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 13 March 2018 21:17:03 UTC
The current version of the Fetch Living Standard indicates `Downlink` is [safelisted request header](https://fetch.spec.whatwg.org/#cors-safelisted-request-header) and links to `Downlink` in the [HTTP Client Hints](http://httpwg.org/http-extensions/client-hints.html) draft. However, `Downlink` has since been removed from the Client Hints. ([merge](https://github.com/httpwg/http-extensions/pull/361), [commit](https://github.com/httpwg/http-extensions/commit/b8143222fbd427eb46ad51e0cb0fd79f1746075d)) Should `Downlink` be removed from the safelisted request headers; or, should the Fetch LS link to the NetInfo API ([here](http://wicg.github.io/netinfo/#-dfn-downlink-dfn-attribute))? (Although, there it is an attribute, and not a header.) (FWIW I'm not following any of the WG draft discussion, but rather, came across this after reading then wanting to update the [MDN CORS documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). Also, somewhat related, `Last-Event-Id` is also listed on MDN as a safelisted request header, although it still appears to be [forthcoming](https://github.com/whatwg/fetch/pull/597) in Fetch LS.) -- 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/684
Received on Tuesday, 13 March 2018 21:17:03 UTC