Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I'm debugging an API I'm building using netcat to send raw HTTP requests. The thing is that Apache closes the connection after 10 seconds, giving me very little time to type. I know that I could pipe a file to nc, or use any other workaround, but I'd like it to work as it's supposed to.

The Timeout directive in apache2.conf is at its default of 300 seconds, KeetAliveTimeout at 15 seconds. Where could this 10 second timeout possibly be defined? I'm running Ubuntu 10.04 Desktop.



share|improve this question
Do you have any firewall between the box where you're running the netcat and the Apache box? I've seen cases in which the "idle timeout" in the firewall was set too low. – Marco Ramos May 30 '10 at 13:55
I don't think I do, when I sniff it with Wireshark it's the process on port 80 (Apache) that closes the connection. I run both client and server on the same box at the moment, so I imagine Wireshark would pick up any intermediaries. – Andreas Jansson May 30 '10 at 18:57
up vote 3 down vote accepted

This sounds like mod_reqtimeout needs some tweaking. Take a look at the docs for mod_reqtimeout

On ubuntu 10.04, I believe you will find the configuration in:

share|improve this answer
That did the trick, thanks! – Andreas Jansson Jun 1 '10 at 10:57

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.