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

Re: I-D Action: draft-nottingham-http-new-status-00.txt

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 16 Aug 2011 09:47:17 +1000
Cc: ietf-http-wg@w3.org
Message-Id: <7A8B81F0-32A2-4897-892C-2955FDA6C1B1@mnot.net>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>

On 14/08/2011, at 3:03 PM, Mykyta Yevstifeyev wrote:

> Hello Mark,
> 
> I also think APPSAWG can be appropriate for discussion and processing this document.
> 
> I recall the existence of non-standard 444 status code, which stands for 'No Response' and is currently used by nginx servers.  Should we standardize it?  I'll describe briefly.  I suppose the semantics are "due to some reasons the server has chosen to close the connection and return no response to the user"; thus the body in 444 response must be empty.  444 responses must not be stored by the caches, and receiving one should not prevent the user from retrying opening the connection once more.  444 responses should not be generated by intermediaries; they can only be given by the origin servers.

What's the advantage over just closing the connection?


> Another widely-used (and probably even more often than 444) is 509, 'Bandwidth Limit Exceeded'.  This is returned when a server or an intermediary encounters the situation when due to the limitation of the bandwidth it is unable to process client's request or server's response, respectively.  No caching is allowed as well; "Retry-After" may be present.  I think we can standardize this status code as well.

Hmm. I could see this as a server-side version of 'limit exceeded' I suppose... interesting.


> 
> Mykyta Yevstifeyev
> 
>> FYI; a few new status codes.
>> 
>> I suspect this might end up in the APPAWG, since it's out of scope for HTTPBIS.
>> 
>> Cheers,
>> 
>> 
>> 
>> Begin forwarded message:
>> 
>> > From: 
>> internet-drafts@ietf.org
>> 
>> > Subject: I-D Action: draft-nottingham-http-new-status-00.txt
>> > Date: 13 August 2011 5:26:19 PM AEST
>> > To: 
>> i-d-announce@ietf.org
>> 
>> > Reply-To: 
>> internet-drafts@ietf.org
>> 
>> > 
>> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> > 
>> > 	Title           : Additional HTTP Status Codes
>> > 	Author(s)       : Mark Nottingham
>> >                          Roy T. Fielding
>> > 	Filename        : draft-nottingham-http-new-status-00.txt
>> > 	Pages           : 8
>> > 	Date            : 2011-08-13
>> > 
>> >   This document specifies additional HyperText Transfer Protocol (HTTP)
>> >   status codes for a variety of common situations.
>> > 
>> > 
>> > A URL for this Internet-Draft is:
>> > 
>> http://www.ietf.org/internet-drafts/draft-nottingham-http-new-status-00.txt
>> 
>> > 
>> > Internet-Drafts are also available by anonymous FTP at:
>> > 
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> > 
>> > This Internet-Draft can be retrieved at:
>> > 
>> ftp://ftp.ietf.org/internet-drafts/draft-nottingham-http-new-status-00.txt
>> 
>> > _______________________________________________
>> > I-D-Announce mailing list
>> > 
>> I-D-Announce@ietf.org
>> 
>> > 
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> 
>> > Internet-Draft directories: 
>> http://www.ietf.org/shadow.html
>> 
>> > or 
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> 
>> 
>> --
>> Mark Nottingham   
>> http://www.mnot.net/
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Monday, 15 August 2011 23:47:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:46 GMT