Thanks all for taking a look > I have a question about the example in Application-Layer Protocol Settings. The example contains this in the initial response: > > `+ alps=(https://example.com, Device-Memory)` > > But there doesn't appear to be any indication in syntax that this is an encoding of ACCEPT_CH. How is the client to know that? > Did you discuss your proposal with the IETF httpbis WG? @davidben for ALPS and procedure questions > identifying on the initial request that the client supports and is willing to do such redirect would be good. I suppose the hope would be that any browser supporting Client Hints would also support this retry mechanism, but I suppose examining the [browser vendor and major version](https://wicg.github.io/ua-client-hints/) would also do that > Some question we had, what happens when the client hints uses greasing, is that impacting the 'critical' nature of it? (ie: would it remove the greasing part to be more accurate?) Not something we had considered, although an interesting idea. Currently there's not really a notion of a hint being critical or being given more than once changing the value of the hint (that form of state just isn't stored anywhere, nor is any hint being marked "critical") -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/549#issuecomment-768443477
Received on Wednesday, 27 January 2021 17:23:26 UTC