- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 2 Jul 2014 16:02:18 +1000
- To: "Julian F. Reschke" <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 2 Jul 2014, at 3:58 pm, Julian Reschke <julian.reschke@gmx.de> wrote: >> The feeling in the room in Seattle AIUI was that non-final status codes are a signalling mechanism that is no longer necessary in HTTP/2, since the framing layer can do a better job at these tasks. As such, we do not plan to accommodate non-final status codes (1xx) in HTTP/2.0, but instead will give advice about how they can be handled by intermediaries doing transitions between 1.x and 2.x (with one example above). > > That advice isn't there. What can an intermediary do with a new 1xx status code other than dropping it? That was referring to the specific cases that are in use, not the class. Can you compose a pull request outlining what you'd like to see, so we can get a sense of how intrusive it would be, and how likely it is that it'd be supported? Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 2 July 2014 06:02:46 UTC