[Setup] Login details don't stay/cookie not set? for Plone behind Apache-Squid-Pound

[Shayan Raghavjee]

Hi,

I've just deployed Plone 2.5 over an existing Plone 2.0 setup. It's the 
usual Apache-Squid-Pound stack followed by 3 zope instances & a zeo.

Authentication worked fine on the old site, however on the new one, it 
doesn't. The login process goes fine and Plone says the user has been 
logged in. However when you navigate to another page, it loses the 
details. Auth when connecting directly to Plone works fine, so I assume 
there's something in the stack that's a bit off.

As mentioned earlier, the deployment took the place of an old server 
using a Data.fs that I migrated. This is where the complication may be. 
The old plone site is still on the Data.fs for fallback purposes and 
there's a new Plone site which Apache directs to.

The old url was www.durban.gov.za/eThekwini (eThekwini being the id of 
the old plone site) and the new URL is www.durban.gov.za/durban. I 
needed to ensure that any bookmarked URL redirected eThekwini to Durban 
so I added a rewrite rule in Apache, I've quoted my .conf settings 
below, the first rewrites any URL with the eThekwini path to durban, the 
2nd directs to VirtualHostMonster.

RewriteEngine On
# production zope instance
RewriteRule ^/eThekwini(.*) /durban$1

RewriteRule ^/durban(.*) 
http://127.0.0.1:8000/VirtualHostBase/http/%{SERVER_NAME}:80/durban/$1 [L,P]

Can anybody see anything wrong there, it's pretty much exactly what was 
there before except for the RewriteRule.

Thanks for any help,
Shayan