6.0.0-alpha14
7/2/25

[#8543] Infinite loop in login
Summary Infinite loop in login
Queue Horde Base
Queue Version 3.3.4
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester lameventanas (at) yahoo (dot) com
Created 08/31/2009 (5784 days ago)
Due
Updated 09/04/2009 (5780 days ago)
Assigned
Resolved 08/31/2009 (5784 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/04/2009 01:38:10 PM lameventanas (at) yahoo (dot) com Comment #3 Reply to this comment
Please use the mailing list to ask for support.
http://www.horde.org/mail/ contains a list of all available mailing lists.
Already did that before submitting this bug, got nothing useful out of it.

Do you have any information that could be of help here?
08/31/2009 07:45:36 AM Jan Schneider Comment #2
State ⇒ Not A Bug
Reply to this comment
Please use the mailing list to ask for support.

http://www.horde.org/mail/ contains a list of all available mailing lists.
08/31/2009 12:37:27 AM lameventanas (at) yahoo (dot) com Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Infinite loop in login
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
I'm trying to install horde 3.3.4 in a linux machine, distro is suse 11.



Apache and php configuration is the standard one, there are no strange 
redirects, rewrites, etc configured.

I have followed each step closely, there are no missing requirements



Whenever I try to log in for the first time, I get an infinite loop:

index.php -> login.php -> index.php ...



I think the problem is index.php thinks I'm not authenticated, while 
login.php does.



If I comment this section in login.php:



/* Try transparent authentication. */

if (Auth::isAuthenticated()) {

     require HORDE_BASE . '/index.php';

     exit;

}



The loop breaks, but of course the application doesn't work.



I have read similar reports by people installing horde in the webroot.

For me it doesn't make any difference, I get the same behavior by 
using webroot='', or webroot='horde'.



I tried using the default cookie path, as well as '/horde', I still 
get the loop.



I have installed previous versions of horde in the past, even written 
modules using the framework, and never came across this one before.


Saved Queries