[Tickets #2458] NEW: "Redirection limit for this URL exceeded."

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2458
-----------------------------------------------------------------------
 Ticket             | 2458
 Created By         | horde-bugs at iansealy.com
 Summary            | "Redirection limit for this URL exceeded."
 Queue              | Horde Framework Packages
 Version            | FRAMEWORK_3
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


horde-bugs at iansealy.com (2005-08-16 10:28) wrote:

Hi,

I've just upgraded from Horde 3.0.4 to 3.0.5 (and from Nag 2.0.1 to 2.0.2
and from Turba 2.0.2 to 2.0.3). I now can't login. When I try I just get an
error from the browser:

Redirection limit for this URL exceeded. Unable to load the requested page.
This may be caused by cookies that are blocked.

I'm using PHP 4.4.0, but (unusually, I suspect), I'm running the FastCGI
version of PHP.

Here's the output from HEAD:

xxx at xxx:~ $ HEAD http://xxx.dreamhosters.com/horde/
302 Found
Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0
Connection: close
Date: Tue, 16 Aug 2005 17:25:15 GMT
Pragma: no-cache
Location:
http://xxx.dreamhosters.com/horde/login.php?Horde=47d2a9c8433cabd829d7d4e727
c59b29
Server: Apache/1.3.31 (Unix) DAV/1.0.3 mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a
PHP/4.3.10 mod_ssl/2.8.19 OpenSSL/0.9.6c
Content-Type: text/html; charset=ISO-8859-1
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Client-Date: Tue, 16 Aug 2005 17:25:15 GMT
Client-Peer: 64.111.105.157:80
Client-Response-Num: 1
Client-Warning: Redirect loop detected (max_redirect = 7)
Set-Cookie: auth_key=47d2a9c8433cabd829d7d4e727c59b29; path=/horde;
domain=xxx.dreamhosters.com
X-Powered-By: PHP/4.4.0

I thought the patch for bug 2401 might fix this, but the copy of
horde-3.0.5.tar.gz I downloaded yesterday surprisingly already seems to have
had the patch applied.

Cheers,
Ian