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

#303: Generic semantics for the 400 status code (also #302)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 28 Jul 2013 11:45:09 +0200
Message-ID: <51F4E825.1080106@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2012-02-06 09:24, Julian Reschke wrote:
> On 2012-02-05 22:21, Mark Nottingham wrote:
>> Works for me.
>
> -> <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1526>

So in draft -21 it read:

"The server cannot or will not process the request, due to a client 
error (e.g., malformed syntax)." -- 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-21.html#rfc.section.7.5.1>

In draft -22 this was changed to

"The 400 (Bad Request) status code indicates that the server cannot or 
will not process the request because the received syntax is invalid, 
nonsensical, or exceeds some limitation on what the server is willing to 
process." -- 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-22.html#rfc.section.6.5.1>

I'll change that to

""The 400 (Bad Request) status code indicates that the server cannot or 
will not process the request, due to a client error (e.g., malformed 
syntax)."

Best regards, Julian
Received on Sunday, 28 July 2013 09:45:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:14 UTC