My experience is that developers find the whole Accept-* and Vary system to be the most confusing part of HTTP, and adding a new response header with a similar name to those which have until now only been used in the request (to my knowledge!) adds to that confusion, imho. I’m also generally having an ick reaction to the idea of a response including metadata that is nothing to do with the resource but is intended to negotiate the client’s behaviour in future requests. This seems like something that should happen prior to the request, like the way we upgrade to H2, for example. This concern would be mitigated by doing this opt in via origin policy, so I wonder if that could offer a better solution. I don’t know if any of that qualifies as an unambiguous win. -- 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/206#issuecomment-340189620
Received on Saturday, 28 October 2017 13:07:21 UTC