Have you ensured:
HostnameLookups Off
is set in your Apache config? This delay seems symptomatic of Apache (or
the application it's providing) doing a reverse lookup for the calling
IP, and timing out. Subsequent connections in the same session will then
be fine as the resolver libraries will cac
Gerry Reno wrote:
> Right now it's just Apache. The only thing I have to go on is the httpd
> access log:
> 192.168.2.102 - - [24/Jul/2007:19:59:54 -0400] "GET /gw/ HTTP/1.1" 302 -
> 192.168.2.102 - - [24/Jul/2007:19:59:55 -0400] "GET
> /gw/login.php?cd=10&forward=%2Findex.php HTTP/1.1" 200 4742
Rob wrote:
> This is why I always recommend (and try myself) to use thttpd and a single
> image and hand coded html page to do initial _and_ ongoing testing.
>
> So for instance, I'll run thttpd permanently on port 8088 or something so
> that
> if the app is going slow then you can test the timi
Graeme Fowler wrote:
> Have you ensured:
>
> HostnameLookups Off
>
Hi Graeme,
Yes, I have checked and HostnameLookups is off. I have done some
tweaking to the original application and now the first accesses are down
below 15 seconds which is tolerable. It is a large groupware app and
they are
