Hi,sorry to trouble again. I used "QS_SrvMaxConn" parameter in mod_qos to restrict sessions, it does restriction but based on HTTP TCP connection based, but I would like to restrict session based. Apache has to count the persistent connection with back-end server and then restrict further connections.is this feasible to consider the persistent connection after authentication done by webblogic, may be through cookie?Regards,VelRegards,Velmurugan Dhakshnamoorthy (Vel)Singapore.On Thu, Apr 27, 2017 at 5:03 PM, Luca Toscano <toscano.luca@xxxxxxxxx> wrote:Hi!The closest option seems to be http://mod-qos.sourceforge.net/#connectionlevelcontrol but I don't have a lot of experience about it so you'll need to make some tests :)Luca2017-04-26 13:29 GMT+02:00 Velmurugan Dhakshnamoorthy <dvel.hex@xxxxxxxxx>:Thanks Luca, your help is much appreciated.I was able to compile and load mod_qos in Apache 2.4.25 proxy.There are many parameters related to QOS, I am trying to implement a parameter to restrict HTTP session beyond specified limit, example I would like to allow only maximum 100 connections, beyond that should throw an error.Regards,VelOn Apr 21, 2017 18:52, "Luca Toscano" <toscano.luca@xxxxxxxxx> wrote:Hi,I think that you'd just need to install httpd without any reference to mod_qos (that is a third party module, so configure is not aware of it) and finally use apxs to compile/install the new module (more info in https://httpd.apache.org/docs/2.4/programs/apxs.html ).I'd also suggest to test it with httpd 2.4.25 rather than 2.2.27 :)Hope that helps!Luca2017-04-21 8:29 GMT+02:00 Velmurugan Dhakshnamoorthy <dvel.hex@xxxxxxxxx>:Hi Luca,I am trying to use the mod_qos mod_qos-11.39. Is this applicable for Apache 2.4.25 reverse proxy in Red Hat Enterprise Linux 7.2. I followed the below command. however, mod_qos.so file is not getting created though I don't see any error with below commands. I am using non-root privileged account.I tried compiling it using "apxs -i -c mod_qos.c -lcrypto -lpcre" , but could not succeed.any help ?tar xfz httpd-2.2.27.tar.gz
tar xfz mod_qos-11.39-src.tar.gz
ln -s httpd-2.2.27 httpd
cd httpd
mkdir modules/qos
cp ../mod_qos-11.39/apache2/* modules/qos
./buildconf
./configure --with-mpm=worker --enable-so --enable-qos=shared --enable-ssl --enable-unique-id
makeRegards,Velmurugan Dhakshnamoorthy (Vel)Singapore.On Tue, Apr 18, 2017 at 2:51 PM, Luca Toscano <toscano.luca@xxxxxxxxx> wrote:Not sure what is the status of mod_qos (third party module), but you might want to give it a try and see if it fits your needs!Luca2017-04-17 3:08 GMT+02:00 Velmurugan Dhakshnamoorthy <dvel.hex@xxxxxxxxx>:Dear All,Any specific setup to cut and disallow the the further HTTP connections after specified limit (ex: 50 sessions?).My requirement is to allow only 50 users and 51st user should get a custom error message to login after sometime.Regards,VelOn Mar 16, 2017 21:30, "Velmurugan Dhakshnamoorthy" <dvel.hex@xxxxxxxxx> wrote:Thanks for response,Yes my requirement is to completely restrict/disalllow any further connections, example I want to allow only 50 sessions, 51st connection should get an error message to login later after certain period of time.Regards,VelOn Mar 16, 2017 18:58, "Nick Kew" <niq@xxxxxxxxxx> wrote:On Thu, 2017-03-16 at 02:05 +0100, Daniel wrote:
> See about mpm settings/directives such as MaxRequestWorkers, which
> will limit the number of concurrent requests your server can take.
Indeed, but I don't think that's what the OP is looking for in an
apache proxy. Rather the proxy reply with a "too busy" error page
than not take the connection at all, right?
The proxy balancer would be a place to look: that offers various
ways to determine how much traffic to send to a backend. If that
doesn't meet your needs, there are several third-party traffic-
limiting modules.
--
Nick Kew
------------------------------------------------------------ ---------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|