I’m setting up a new Apache server.
If I set the MaxClients definition to, let’s say, one – does it then block anyone who else who tries to connect to my Apache server except for that one person?
Thanks for answers
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m setting up a new Apache server.
If I set the MaxClients definition to, let’s say, one – does it then block anyone who else who tries to connect to my Apache server except for that one person?
Thanks for answers
Yes, you’ll get only one request handled by apache, if you put a quite long KeepAlive Timeout the process will be held for that amount of time by the user. The 2nd user will get his request done by apache only when the first one is finished (or when the keepAlive Timeout ends if the request is in keepAlive mode). So with a small KeepAlive setting, if the requests are fast to handle, you could have a lot of users, done one after the other, without knowing apache handles only one request in parallel.
If you make some activity in the first connection you may be able to block the 2nd request for a very long time.
Now, you should’nt consider it as a way to restrict access to one dedicated person, it’s not a security feature. You rely on TCP/IP connections, if the connection breaks, then the 2nd user may get access to the server.