Re: "Too Busy" Error Needed

altis@ibeam.jf.intel.com (Kevin Altis)

Mail folder: WWW Talk Apr 94-present
Next message: Nick Arnett: "Re: www-philosophy @ wit ?"
Previous message: Marc VanHeyningen: "Re: "Too Busy" Error Needed "
Maybe in reply to: Bob Denny: ""Too Busy" Error Needed"
Reply: Henrik Frystyk Nielsen: "Re: "Too Busy" Error Needed"

Errors-To: listmaster@www0.cern.ch
Date: Thu, 9 Jun 1994 03:04:31 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <m0qBYV2-0003deC@ibeam.intel.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: altis@ibeam.jf.intel.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: altis@ibeam.jf.intel.com (Kevin Altis)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: "Too Busy" Error Needed
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset="us-ascii"
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
Mime-Version: 1.0

At  2:03 AM 6/9/94 +0200, Marc VanHeyningen wrote:
>> There are situations when an HTTP server may want to indicate that it is too
>> busy to accept a request. There is no code for this defined in the HTTP2
>spec.
>> Taking the "spirit" of the 400 vs 500 errors, since this is a server
>> "problem", it seems like the 500 series is appropriate.
>
>Sounds reasonable.

This error message is also a good way to indicate when a proxy server is
unable to complete an FTP transaction because the remote FTP server has
reached its user limit. Currently this is reported as a 500 error.

For completeness sake, I would like to see this response added to the HTTP
specification.

ka