- From: Stefan Eissing <stefan.eissing@greenbytes.de>
- Date: Thu, 18 Dec 2014 10:34:16 +0100
- To: Eliot Lear <lear@cisco.com>
- Cc: Bray Tim <tbray@textuality.com>, Yoav Nir <ynir.ietf@gmail.com>, Mark Nottingham <mnot@mnot.net>, Niels ten Oever <lists@digitaldissidents.org>, HTTP Working Group <ietf-http-wg@w3.org>
> Am 18.12.2014 um 10:12 schrieb Eliot Lear <lear@cisco.com>: > [...] I did, however, ask questions in order to understand what programmatic behavior you expect in reaction to this response code that would differ from at least one existing response code. To me at least, that's what these low level HTTP response codes are for, and I probed whether the code could be generalized. [...] Can you give examples in the description of existing codes like 402, 403, 404, 405, 406, 408, 409, 413, 414 about what you expect this draft to do for 451 beyond what is there? I regard the 451 documentation to be in the spirit of the other HTTP status code documentations, so I do not see your problem. //Stefan <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Received on Thursday, 18 December 2014 09:34:40 UTC