W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: #535: No 1xx Status Codes

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 02 Jul 2014 08:40:51 +0200
Message-ID: <53B3A973.70403@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2014-07-02 08:30, Mark Nottingham wrote:
> ...
> An alternative resolution would be to mint a new, short consensus document that disallows minting new 1xx status codes -- due to the fact that they're not well-supported in implementations nor APIs, nor intermediaries (IIRC).
> ...

Do you have evidence of implementations that break on new 1xx codes?

I agree that APIs are a problem, but we have the same problem for 
trailers (which we keep), and anything that's new in the HTTP/2 world 
will need new APIs as well, so I'm not sure how that is a compelling 
argument.

Best regards, Julian
Received on Wednesday, 2 July 2014 06:41:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC