- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 23 May 2014 06:51:13 -0700
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Roland Zink <roland@zinks.de>, HTTP Working Group <ietf-http-wg@w3.org>
On 22 May 2014 18:21, Mark Nottingham <mnot@mnot.net> wrote: > We already have a HTTP status code for this: <http://tools.ietf.org/html/rfc6585#section-5> I always forget about those... > Why push it down into the framing layer? Only because I forgot about those... Let me try the PR again. That's in part why I made it a PR rather than a direct edit :) I think that the documentation of the problem is still OK, just the reporting/handling part. I'll note that 431 isn't an option for a client or intermediary that gets bombed by a server, but I guess the implication there is that the response is simply unusable in that case.
Received on Friday, 23 May 2014 13:51:43 UTC