Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 67956 invoked from network); 27 Jun 2007 20:37:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2007 20:37:51 -0000 Received: (qmail 53882 invoked by uid 500); 27 Jun 2007 20:37:41 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 53865 invoked by uid 500); 27 Jun 2007 20:37:41 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 53854 invoked by uid 99); 27 Jun 2007 20:37:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2007 13:37:41 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of sbhobbs@uga.edu designates 128.192.1.109 as permitted sender) Received: from [128.192.1.109] (HELO puntd3.cc.uga.edu) (128.192.1.109) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2007 13:37:37 -0700 Received: from [127.0.0.1] (asgfw.ucns.uga.edu [128.192.88.205]) by puntd3.cc.uga.edu (MOS 3.8.4-GA) with ESMTP id CQA10909; Wed, 27 Jun 2007 16:37:16 -0400 (EDT) Message-ID: <4682CA7C.60909@uga.edu> Date: Wed, 27 Jun 2007 16:37:16 -0400 From: Brantley Hobbs Reply-To: sbhobbs@uga.edu Organization: ASG User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Keeping busy site responsive References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org You know, I hadn't given it a lot of thought to be honest. I think that for accuracy's sake it should probably be a 500 error (I assume that 503 is a server busy error or something; don't know it off the top of my head). An actual redirect error could confuse a browser. I'd assume that for optimal performance you'd want to redirect to another machine, but there's nothing enforcing this. If you're using Apache or IIS as a localhost front-end, you could redirect to a URI that's being served by the web server. This is likely to be a low-cost operation. Brantley Nelson, Tracy M. wrote: > | From: Brantley Hobbs [mailto:sbhobbs@uga.edu] > | Sent: Wednesday, 27 June, 2007 12:37 > | > | This approach seems to work well (at least until the box staggers to a > | halt simply issuing redirects). > > Just out of curiosity, do you think it would help in those situations to > issue a 503 instead of a 307? Or do you redirect to another machine for > the busy page? > ----------------------------------------- > ------------------------------------------------------------ > The information contained in this message is confidential > proprietary property of Nelnet, Inc. and its affiliated > companies (Nelnet) and is intended for the recipient only. > Any reproduction, forwarding, or copying without the express > permission of Nelnet is strictly prohibited. If you have > received this communication in error, please notify us > immediately by replying to this e-mail. > ------------------------------------------------------------ > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org