Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 94922 invoked from network); 6 Oct 2008 11:31:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Oct 2008 11:31:52 -0000 Received: (qmail 68228 invoked by uid 500); 6 Oct 2008 11:31:41 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 67859 invoked by uid 500); 6 Oct 2008 11:31:40 -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 67848 invoked by uid 99); 6 Oct 2008 11:31:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 04:31:39 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=DNS_FROM_OPENWHOIS,DNS_FROM_SECURITYSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 11:30:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KmoIx-0004MJ-NQ for users@tomcat.apache.org; Mon, 06 Oct 2008 04:31:11 -0700 Message-ID: <19836189.post@talk.nabble.com> Date: Mon, 6 Oct 2008 04:31:11 -0700 (PDT) From: colin_ To: users@tomcat.apache.org Subject: how to avoid multiple requests from the same client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: colioni@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org hello everyone while testing our website (running with a java servlet) i noticed that an impacient user could overload our database server. since some sites need alot of time to load, an impacient user can click multiple times on the same link. i thought tomcat would notice this, and block the further requests and only respond to the first. but tomcat really seems to handle every single request! my question is, where to prohibit this possible overload. is it a tomcat-configuration issue, or mine due to false request handling? i'm running apache tomcat 5.5 with catalina. -- View this message in context: http://www.nabble.com/how-to-avoid-multiple-requests-from-the-same-client-tp19836189p19836189.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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