This may have been reported before. If so, I never saw the report.
We discovered that enabling the Configuration Directive
may cause a 30-second hang per connection (not request) if the remote
site has not properly configured the ident daemon. It's unclear exactly
why this is. We're supposing that at these sites, the identd has been
left in the services and inetd.conf files (or equivalents) but there is
no identd actually running. The 30 seconds may be the timeout.
In any case, a few points are clear
* It doesn't occur in every case
* It occurs only at a few sites (shore.net being identified as one of
them, not to single them out but to provide a test case)
* Setting IdentityCheck to No removes the problem entirely
In the CERN httpd 3.0 docs, it mentions that enabling this directive
might cause some delays. But 30 seconds seems excessive. I'm sure
hacking the daemon would make it possible to have 500 ms timeout or
some such on the server end.
Glenn Fleishman * Point of Presence Company <http://www.popco.com>
Contributing Editor, Adobe Magazine
Moderator, Internet marketing list and Web Critique list