Le mar 11/02/2003 � 13:15, Marcel Pol a �crit : > > > What about mod_iplimitconn? > > > http://dominia.org/djao/limitipconn2.html > > Ahh, that one. Yes I looked at it, but it requires that you patch the apache > > core. I'm not comfortable with that, maybe jmdault has more good points on > > this. Apache2 is soon to be moved to main, and then I can't touch it as > > easy, but I don't want to sneak in a patch just to make this module work. > > It's better to wait until the module author(s) fix the module so that you > > don't have to patch the apache core I think.
I had a look at the patch, it's very very small (69 lines), and touches only mod_status. So I have no problem patching Apache with this. I'll see if I can add it before the feature freeze and RC1. Jean-Michel > > That was my first impression too, but the patch for apache is only necessary > for clients using proxies. Without the apache patch, 2 clients using the same > proxy will be counted as the same client. This would only affect high-traffic > sites, which you can call a limitation. For not-so-high-traffic sites, it > shouldn't be a big problem. > > > > I believe I used mod_throttle or mod_bandwidth once, and was dissapointed > > > that it just refuses connections after the limits have been reached (or > > > was that user error?). > > > I haven't used mod_iplimitconn myself, but it seems to be a good way to > > > set a maximum to connections per client adress. > > > > Have you tried mod_bwshare yet? > > http://www.deserve-it.com/third_party_modules_for_apache2_1.html > > No, I haven't. According to the docs on the site it seems good. It at least > gives a usefull error :-) Better then "connection refused" or something. I > should try it out. > > -- > Marcel Pol > >
