[whatwg/fetch] Integrate Acccept-CH-Lifetime to populate "client hint list" (#566)

Related notes and discussion from [blink-dev thread](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/QHI3sio6--Q)..

> On Thursday, June 29, 2017 at 12:25:06 AM UTC-7, Ilya Grigorik wrote:
>> On Thu, Jun 29, 2017 at 5:02 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>>> On Thu, Jun 22, 2017 at 2:32 PM, Tarun Bansal <tbansal@chromium.org> wrote:
>>> Spec
>>> https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-04#section-6.2
>>
>> It seems this would also require corresponding changes to Fetch?
> 
> I think we already have correct logic [1] within the fetch algorithm. However, there is a missing bit  there for how "client hint list" [2] is populated, which is what this update is implicitly tackling. We  previously said that this will be defined upstream in the IETF doc, but in retrospect.. I don't think that makes sense, as we're missing all the necessary hooks there. If it makes sense to you, I'd propose we integrate this logic as part of Fetch. WDYT?
>
> [1] https://fetch.spec.whatwg.org/#dfnReturnLink-1
> [2] https://fetch.spec.whatwg.org/#client-hints-list

...

> On Thursday, June 29, 2017 at 7:27:54 AM UTC-7, Anne van Kesteren wrote:
> Sounds good. Since it's a response header the other part I was 
> thinking of is defining when it's parsed/handled. In particular 
> whether it's handled in responses from service workers or only in 
> responses from the network. 


-- 
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/566