Re: Server Push Error Codes

> On 24 Aug 2016, at 3:30 PM, Martin Thomson <> wrote:
> These seem mostly reasonable.
> On 24 August 2016 at 14:26, Mark Nottingham <> wrote:
> We are looking to provide solutions that make this unnecessary (absent
> outright errors), but I think that it's a good code to have.

Yeah, I'm thinking more for outright error cases; when a server is misconfigured or mis-implemented, to save the admin / dev from banging their head against the wall too much.

> 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.

Possibly. I don't disagree with anything you say, it's just that error codes are pretty cheap, and the places that these are going to be useful are dark corner cases that are really atypical.

> 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.

Except when it's not. :)

> 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.

Yeah, I didn't see much value in providing CONTENT_TYPE_NOT_SUPPORTED for that reason.

More than anything with these, I'm interested in collecting stats on them, to see how prevalent these sorts of problems are. If they aren't used, that's good news.


Mark Nottingham

Received on Wednesday, 24 August 2016 05:40:21 UTC