- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 24 Aug 2016 15:30:28 +1000
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
These seem mostly reasonable. On 24 August 2016 at 14:26, Mark Nottingham <mnot@mnot.net> wrote: > # PUSH_UNAUTHORITATIVE We are looking to provide solutions that make this unnecessary (absent outright errors), but I think that it's a good code to have. > # PUSH_CONTENT_ENCODING_NOT_SUPPORTED This seems like it could be overly specific. PUSH_NOT_ACCEPTABLE might be used to cover Accept as well as Accept-Encoding. Unless you want both. For content-encoding, it seems unlikely that the server will get this wrong. The server might reasonably assume that the value for Accept-Encoding is constant and it will usually be right. If not, read on. For Accept, a server might get it wrong, but it is probably the case that the right machinery for determining whether a response is acceptable isn't engaged when the push arrives. That usually requires a bunch of other context. The same applies if Accept-Encoding isn't constant.
Received on Wednesday, 24 August 2016 05:30:58 UTC