Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So that subsequent request can still use the current connection.

share|improve this question
You should accept the answer that best answered your question. You can do this by clicking the white check in front of the answer. – Saif Bechan Apr 2 '10 at 10:13

The KeepAlive option controls whether connections are kept open after a request. KeepAliveTimeout controls how long Apache will wait for a subsequent request.

share|improve this answer

You need to set

KeepAlive On

share|improve this answer

According to the Official Apache Documentation, it would depend on the programming of the "thing" connecting to the apache server. Thus HTTP/1.0 source programming will have some difficulty in doing what you are asking....whereas HTTP/1.1 protocol programming will make it easier to make this happen.

" For HTTP/1.0 clients, Keep-Alive connections will only be used if they are specifically requested by a client. In addition, a Keep-Alive connection with an HTTP/1.0 client can only be used when the length of the content is known in advance. This implies that dynamic content such as CGI output, SSI pages, and server-generated directory listings will generally not use Keep-Alive connections to HTTP/1.0 clients. For HTTP/1.1 clients, persistent connections are the default unless otherwise specified. If the client requests it, chunked encoding will be used in order to send content of unknown length over persistent connections. "

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.