"Too Busy" Error Needed

• Mail folder: WWW Talk Apr 94-present
• Next message: Marc VanHeyningen: "Re: SECURITY ALERT! [Re: How do you execute shell scripts in Mosaic] "
• Previous message: Vinay Kumar: "Re: SECURITY ALERT! [Re: How do you execute shell scripts in Mosaic]"
• Reply: Kevin Altis: "Re: "Too Busy" Error Needed"

Errors-To: listmaster@www0.cern.ch
Date: Wed, 8 Jun 1994 22:12:14 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <Chameleon.4.00.4.940608125103.rdenny@bob386.alisa.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: rdenny@netcom.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Bob Denny <rdenny@netcom.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: "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
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.

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.

The Windows httpd (v1.2b8 and later) reports when it is too busy to accept 
another request by returning a "503 Too Busy", followed by a short HTML 
message. What it means is that there are already 8 active transactions, the 
server's limit. The error is returned in the server dispatcher thread without 
starting any new transaction threads.

If nobody argues, I'll leave it that way. It ought to get added to the spec.

  -- Bob