From owner-freebsd-isp Wed Aug 19 23:41:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02424 for freebsd-isp-outgoing; Wed, 19 Aug 1998 23:41:10 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from main.piter.net (main.piter.net [195.201.22.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02395 for ; Wed, 19 Aug 1998 23:41:00 -0700 (PDT) (envelope-from cyril@main.piter.net) Received: (from cyril@localhost) by main.piter.net (8.8.7/8.8.7) id KAA23380; Thu, 20 Aug 1998 10:47:12 +0400 (MSD) (envelope-from cyril) Date: Thu, 20 Aug 1998 10:47:12 +0400 (MSD) From: "Cyril A. Vechera" Message-Id: <199808200647.KAA23380@main.piter.net> To: graeme@echidna.com Subject: Re: Rate limiting HTTP requests Cc: freebsd-isp@FreeBSD.ORG Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is there any mechanism possible in FreeBSD or Apache, for limiting the > rate at which HTTP GET requests are served? try to use ipltd version 2.0 or higher (with ipfw). It can limit as bandwidth, as packets number per second. [...] > users) so as to keep the peak data rate under some set limit. The rate > limiting criterion could be based on degrading service for any accessor > (remote IP) generating more than a certain level of traffic on a > sustained basis. with ipfw you can create rules, that filters out packets from search engines (depending on its' IPs) and than divert the packets to ipltd. last ipltd verios can be found on http://sply.piter.net Sincerely your, Cyril A. Vechera email:cyril@piter.net --------- http://sply.piter.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message