RE: Mod_throttle - is this really what I need?
http://www.snert.com/Software/mod_throttle/
"This Apache module is intended to reduce the load on your server &
bandwidth generated by popular virtual hosts, directories, locations, or
users according to supported polices that decide when to delay or refuse
requests. Also mod_throttle can track and throttle incoming connections
by IP address or by authenticated remote user. "
It doesn't do bandwidth shaping, ie: only allowing a maximum transfer of
56K per connection.
It's really designed for things like spiders, or offline browsers that
are downloading too much from your web site too fast - and tying up your
bandwidth and server resources.
Carl
-----Original Message-----
From: SpArTaK [mailto:spartak@comcast.net]
Sent: 07 May 2003 04:56
To: debian-apache@lists.debian.org
Subject: Re: Mod_throttle - is this really what I need?
I tried the below and yeilds no results it the file downloads at maximum
speed
and then locks out the web site from bieng accessed again due to the
mod_throttle lock for too much downloaded or soemthing. I have spend
many
hours trying to find out how to set a limit on the bandwidth used and
have
found some configs that DO NOT WORK and very little info on why this is
so
cryptic. Can someone out there plese give us some more info on how to
use
this to limit "stuff" in apache any examples or sources of information
except
the /usr/share/doc/appache-common/index.htm file would be helpfull
thanks in
advance!
-- Vladi
On Thursday 06 February 2003 12:27 pm, dwokfur@dc.sote.hu wrote:
> Greetings to debianer apachers,
>
> My aim was to limit the bandwith to my apache web server. According to
the
> descriptions I figured out, that mod_throttle is the tool I probably
> looking for. So I RTFMed, and tried to set it up. Here are the lines
> important from this point of view pasted out from my apache config:
> LoadModule throttle_module /usr/lib/apache/1.3/mod_throttle.so
>
> # Throttle
> <IfModule mod_throttle.c>
> ThrottleMaxDelay 10
> ThrottlePolicy None
> <Location /throttle-status>
> SetHandler throttle-status
> </Location>
> </IfModule>
>
> <Directory /var/www/throttle>
> ThrottlePolicy Speed 50 1
> </Directory>
>
> The result. Throttle-status reflects the config I set up correctly.
But
> when I download a big file from the /throttle directory, it comes with
120
> to 600 kbytes/sec depending on the actual network usage between the
two
> places. Then the directory becomes unavaiable for a long time.What did
I
> miss? I configured 50 kbytes/sec! It doesn't take effect for the first
> connection and it makes the directory unavail? How does it makes
sense?
> I've tried different policies (Original, Speed, Volume), and also
tried
> ThrottleClientIP with the same results.Has anyone managed to do this
for
> his/her first connecion? What did I do wrong? Did I miss an important
> option
> (EnableThrottleFromTheVeryBeginning)?
> I wanted traffic shapeing. Is this module really for bandwidth
limiting?
> Because if it behaves correctly as I see, I can say, that this is only
a
> request delayer, not a throttler. Is there an apache module for this
> purpose (limit a directory to 50 kbytes/sec)? I'm sticked to debian.
> LimitIPConn works fine, although.
>
> Thank you 4 your help,
> Dw.
--
To UNSUBSCRIBE, email to debian-apache-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
_____
GMG Regional Digital is part of the Guardian Media Group plc.
CONFIDENTIALITY NOTICE. The information contained in this e-mail is
intended only for spartak@comcast.net, debian-apache@lists.debian.org.
It may contain privileged and confidential information that is exempt
from disclosure by law and if you are not an intended recipient, you
must not copy, distribute or take any action in reliance on it. If you
have received this e-mail in error, you may notify our helpdesk by
telephone on 44 (0)161 211 2222. E-mail transmission cannot be
guaranteed to be secure or error-free. The sender
(carl.johnstone@gmgrd.co.uk) therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of e-mail transmission. If verification is required please
request a hard-copy version.
Reply to: