Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 43809 invoked from network); 10 May 2004 04:50:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 May 2004 04:50:25 -0000 Received: (qmail 33631 invoked by uid 500); 10 May 2004 04:49:59 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 33362 invoked by uid 500); 10 May 2004 04:49:57 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 33337 invoked from network); 10 May 2004 04:49:56 -0000 Received: from unknown (HELO navi.architechies.com) (64.81.33.205) by daedalus.apache.org with SMTP; 10 May 2004 04:49:56 -0000 Received: from [192.168.1.1] (helo=[192.168.1.102]) by navi.architechies.com with esmtp (Exim 3.35 #1 (Debian)) id 1BN25C-0004xd-00 for ; Sun, 09 May 2004 21:08:02 -0700 Message-ID: <409F00F7.3080807@brentdax.com> Date: Sun, 09 May 2004 21:11:35 -0700 From: Brent 'Dax' Royal-Gordon User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en MIME-Version: 1.0 To: users@httpd.apache.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: [users@httpd] Bandwidth control under Apache 2 X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, I am a small-scale sysadmin running an x86-based Debian Linux server with Apache 2.0.48 over an ADSL line. Among the sites on this server is a public file-hosting service, intended for small files such as forum avatars. Recently, a user uploaded several dozen large zip files and posted links on a website. As a result, I got eighty thousand extra requests in one day, all for multi-megabyte files--on a site that usually gets less than 40k hits, requesting files that average 20kb or so. As you can imagine, my DSL line positively freaked out at this. I've since deleted those files (as I write this, I'm watching the HTTP/410 entries in the access log scroll by in another window), but I'd like to take steps to ensure that a file or small collection of files can't monopolize my server's bandwidth in the future. (I want to regulate the flow of traffic out of my server, not place daily/weekly/monthly transfer caps on my users.) Online searches have turned up modules like mod_bandwidth and mod_throttle, but these all seem to be for Apache 1.3. I don't believe that downgrading is an option--I have several sites written in Embperl 2.0, which depends on mod_perl 2, which of course depends on Apache 2. I've tried compiling mod_bandwidth, but the compilation failed rather dramatically. Searching the list archives gave me a thread from January stating that there were no Apache 2 modules to perform this service. Is this still true? If so, how difficult would it be to port one of the Apache 1.3 modules? (Although I've done work in both the Perl 5 and Parrot cores, I'm hardly a C god.) Alternately, how difficult would it be to implement such a module from scratch, and would it be easier (or even possible) to implement in mod_perl? (I am aware of Linux's built-in traffic shaping; however, I haven't been able to get it to work. Feel free to contact me off-list if you want to help me get that working.) Thanks in advance, -- Brent "Dax" Royal-Gordon Perl and Parrot hacker Oceania has always been at war with Eastasia. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org