Seems likely this is not something we can solve in Horde.

No ideas, sorry...

So after much further testing I have actually narrowed the effective 
problem to occur with Apache 2.1.x or 2.2.x. If I keep my PHP 
installation/modules the same, and the same horde sources, when I 
install Apache 2.0.59, it works PERFECT.



I have tested with all three branches for 2.x in FreeBSD 6.2-STABLE -- 
2.0.x works, 2.1.x doesn't, 2.2.x doesn't. I have no clue what would 
change in Apache, as I don't TOUCH the configuration files. Just 
install Apache, re-install PHP 5.2.0 + extensions, launch. 2.0.x works 
out of the box.



Any clues?

I haven't seen this, so it's tough to diagnose unfortunately. Any 
chance you can trace further inside the authenticate() call?



Possibilities, though these are just guesses at this point, is that 
something available to authenticated users is hanging (turba with bad 
ldap configuration?), preferences are very slow, there's a DNS timeout 
...

When logging into Horde 3.2-cvs, there is about a 15 second lag 
between submitting authentication information and actually being 
logged in. This is true for any authentication type, even the included 
'Administrator' stock login. I have also tried with LDAP and FTP, same 
result of 15 second login time.



Using a series of system('date'); print outs, I narrowed it down 
within the login.php file to the area where the authentication 
instance is called to verify credentials.



if ($auth->authenticate(Util::getPost('horde_user'), array('password' 
=> Util::getPost('horde_pass'))))



This execution is where the 15 second delay occurs for sure. Where 
inside of the Auth class it goes wild, is beyond me.



FreeBSD 6.2-Stable, Apache 2.2.4, PHP 5.2.0