Hi all,
I have a problem with setting and deleting cookies which prevents the autologin-feature of gobi to work properly.
On my development server cookie setting and deleting works like it should, but helma is serving requests directly.
The production server setup is a bit more complicated: web requests are served by apache2 which redirects to a helma instance on a proxy port.
The autologin feature of gobi does not work properly, because it seems that apache or helma (or perhaps another proxy) creates 2 cookies, one with the 'www' in front of the domain name, and one without, so the underlying function is caught in a loop of sorts (logout-login; logout-login; since deleting the cookie only reaches one of both).
So I would like to know if anyone has had this type of problem, or has a clue to this strange behaviour, if not a solution ;-)
best wishes,
Janos
