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!
http://mod-qos.sourceforge.net/#requestlevelcontrol Luca 2017-04-17 3:08 GMT+02:00 Velmurugan Dhakshnamoorthy <dvel....@gmail.com>: > 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, > Vel > > On Mar 16, 2017 21:30, "Velmurugan Dhakshnamoorthy" <dvel....@gmail.com> > 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, >> Vel >> >> On Mar 16, 2017 18:58, "Nick Kew" <n...@apache.org> 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-unsubscr...@httpd.apache.org >>> For additional commands, e-mail: users-h...@httpd.apache.org >>> >>>
