Redirect Loop

[andreychek]

I just tried the Network Edition on CentOS 4.2. It works like a champ, except for one oddity (which may or may not have anything to do with CentOS).
I go to this url:

After">http://zimbra.mydomain.com/zimbra/mail
After clicking "login", it ends up dropping the "/mail", and goes into an infinite redirect loop.
However, if I add a parameter to the end of the url (any parameter... I started with "?debug=1", but later tried "?foo=1", it doesn't chop off the end of the url, and ends up working fine.
Nothing shows up in /var/log/zimbra.log.
In /opt/zimbra/log, it shows many events similar to the following:

2005-11-16 15:10:57,612 DEBUG [http-80-Processor96] 

 [ip=xxx.yyy.253.230;name=eric@zimbra.mydomain.com;]

 SoapEngine - dispatch: doc NoOpRequest

I'd give you any debugging output by passing in debug=1 in the url, but that's exactly what prevents the issue from occurring :-)
However, using the live http headers plugin for Firefox, I did capture what's being sent to and from the server, and attached it to this post (I changed the domain name to "mydomain.com", but everything else is exactly the same). You can see the first two requests, which go to /zimbra/soap and /zimbra/auth. After that, it just keeps calling /zimbra/mail (with varying parameters), receiving a "302 Temporarily Moved" error each time.
From this same desktop, using the same browser, I can access another Zimbra server I have that's running the M2 OSS product. Both are running CentOS 4.2. Both were installed from scratch (not upgraded). The only difference I know of is that the one which is acting oddly is the Network version, the one running the OSS version is fine (but again, adding a parameter to the url "fixes" it).
If there's any additional output I can provide, just let me know.
Thanks,

-Eric

zimbra-debug.txt

[14319KevinH]

Hmm no obvious anwsers.. what are the x-cache headers? Are those the extension or some cache your runnnig?

[andreychek]

[quote user="14319KevinH"]Hmm no obvious anwsers.. what are the x-cache headers? Are those the extension or some cache your runnnig?[/QUOTE]

I'm behind a Squid HTTP proxy, so the cache related headers are referring to that.
I was thinking about that too, if Squid could be part of the problem. But it keeps ringing in my head that it's okay for one Zimbra server, but not another.
OTOH, I just tried it from home on my laptop (no proxy), and it worked fine.
I'll take my laptop into work tomorrow, set it up on the proxy, and see if that causes the issue.
Thanks,

-Eric