Re: Getting to Consensus on 1xx Status Codes (#535)

On Wed, Jul 16, 2014 at 10:40 PM, Mark Nottingham <> wrote:

> <>
> So far, we've had two proposals for this issue;
> a) Accommodating non-final responses in HTTP/2
>     See Julian's proposal at <
>> for an idea of how
> this would look in the spec.
> b) Publishing a separate document deprecating 1xx status codes
>     Thereby preventing the establishment of new ones (HTTP/2 already
> defines how to deal with 100, and 101 is not relevant to this protocol. 102
> was dropped by its primary use case, WebDAV, here: <
> I'd like to hear:
> 1) Your preferred outcome (if any)

My preferred outcome is to drop 1xx entirely. We already have the existing
use cases of it covered (or removed from use), so there's no backwards
compatibility issues. (Not that there would have been much, given that 1xx
isn't terribly well supported in the wild, anyway.) And the general space
that 1xx covers seems like something that should be handled at the framing
layer in h2 - in other words, things that are protocol workings.

If anyone wants to support some future 1xx-like thing, that sounds like the
perfect match for an extension. Call the extension frame
"112_PLINY_THE_YOUNGER_DIED" for all I care.

Received on Thursday, 17 July 2014 18:09:59 UTC