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 have setup a location to enable client authentication based on x509 certificates:

<Location /authenticate>
  SSLVerifyClient require
  SSLVerifyDepth 10

The authentication is done by unlocking the smartcard with a PIN. When a user needs more that 30 seconds to unlock his smartcard the response is "No data received". Hitting the reload button works, but most users will run into confusion when they see default browser error page.

How can I modify that timeout to allow longer timeouts?


share|improve this question
Is it reproducibly exactly 30 seconds? – Shane Madden May 31 '12 at 20:51
No not really, if I successfully connect the timeout seems longer, but after a restart I am pretty sure that it is always 30 seconds. Changed already the ttl parameter on the ProxyPass config line to 180 seconds to be sure it is no proxy issue. – tinti Jun 4 '12 at 15:55
Can you get exact time numbers? A packet capture tool like wireshark might be a good way to get this info as well as see exactly where the stall in communication occurs. – Shane Madden Jun 4 '12 at 16:10

Your Answer


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

Browse other questions tagged or ask your own question.