- From: Ilya Grigorik <notifications@github.com>
- Date: Wed, 18 Apr 2018 16:07:59 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 18 April 2018 16:08:22 UTC
Most recent IETF draft updates the opt-in flow. The short of it: - Servers must [advertise Accept-CH with list of hints](http://httpwg.org/http-extensions/draft-ietf-httpbis-client-hints.html#accept-ch) they want to receive. - If this opt-in is present on response to navigation request, then we should emit the requested request header fields for same-origin subresources. - Optionally, the server can also [provide Accept-CH-Lifetime](http://httpwg.org/http-extensions/draft-ietf-httpbis-client-hints.html#rfc.section.2.2.2) to persist above preference. This means that future navigation+subresource requests should emit requested header fields. Sending requested header fields to 3P origins is subject to Feature Policy, the plumbing for which is WIP — see https://github.com/WICG/feature-policy/issues/129. -- 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/707#issuecomment-382441213
Received on Wednesday, 18 April 2018 16:08:22 UTC