[mimp] mimp-HEAD redirects to IMP after login

[Volker Then]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Volker Then <horde at volkerthen.com>:
>
>> here's an excerpt from apache log that shows the redirecting:
>>
>> p07-03.opera-mini.net - - [24/Oct/2006:09:59:12 +0200] "GET  
>> /horde/mimp/ HTTP/1.1" 302 38  
>> "http://myhostname/horde/index.php?url=http%3A%2F%2Fmyhostname%2Fhorde%2Fmimp%2Findex.php" "Opera/8.01 (J2ME/MIDP; Opera Mini/2.0.3920/1376; de; U; ssr)"  
>> "-"
>> p07-03.opera-mini.net - - [24/Oct/2006:09:59:13 +0200] "GET  
>> /horde/imp/redirect.php?actionID=login&autologin=1&server_key=imap  
>> HTTP/1.1" 302 38  
>> "http://myhostname/horde/index.php?url=http%3A%2F%2Fmyhostname%2Fhorde%2Fmimp%2Findex.php" "Opera/8.01 (J2ME/MIDP; Opera Mini/2.0.3920/1376; de; U; ssr)"  
>> "-"
>>
>>
>> Going back and second try gives the correct mimp screen:
>>
>> p07-03.opera-mini.net - - [24/Oct/2006:10:04:18 +0200] "GET  
>> /horde/mimp/ HTTP/1.1" 200 595 "-" "Opera/8.01 (J2ME/MIDP; Opera  
>> Mini/2.0.3920/1376; de; U; ssr)" "-"
>
> So you're using hordeauth with IMP/MIMP? Can you verify if using IMP  
> auth works correctly? If so, sounds like the bug is narrowed to  
> hordeauth staying in IMP when it should redirect elsewhere.  
> Otherwise you should trace on the PHP side, not the HTTP requests,  
> to find out where/why you're being sent wrong.
>

Indeed, if using IMP as horde's authentication backend, there is no  
problem at all. When I use LDAP authentication instead, the  
above-mentioned behavior recurs.

Bug?

Volker