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

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

From: Mykyta Yevstifeyev <evnikita2@gmail.com>
Date: Sun, 14 Aug 2011 08:03:44 +0300
Message-ID: <4E475730.800@gmail.com>
To: ietf-http-wg@w3.org, Mark Nottingham <mnot@mnot.net>
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.

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.

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  <mailto:internet-drafts@ietf.org?Subject=Re%3A%20Fwd%3A%20I-D%20Action%3A%20draft-nottingham-http-new-status-00.txt&In-Reply-To=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E&References=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E>
> >  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  <mailto:i-d-announce@ietf.org?Subject=Re%3A%20Fwd%3A%20I-D%20Action%3A%20draft-nottingham-http-new-status-00.txt&In-Reply-To=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E&References=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E>
> >  Reply-To:internet-drafts@ietf.org  <mailto:internet-drafts@ietf.org?Subject=Re%3A%20Fwd%3A%20I-D%20Action%3A%20draft-nottingham-http-new-status-00.txt&In-Reply-To=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E&References=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E>
> >
> >  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  <mailto:I-D-Announce@ietf.org?Subject=Re%3A%20Fwd%3A%20I-D%20Action%3A%20draft-nottingham-http-new-status-00.txt&In-Reply-To=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E&References=%253C499F702D-445A-4845-BD72-ACED733A6B67%40mnot.net%253E>
> >  https://www.ietf.org/mailman/listinfo/i-d-announce
> >  Internet-Draft directories:http://www.ietf.org/shadow.html
> >  orftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> --
> Mark Nottinghamhttp://www.mnot.net/
Received on Sunday, 14 August 2011 05:03:38 GMT

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