I've seen various posts on the web about running SOGo behind nginx yet I
couldn't find the one difference in my configuration that breaks it for me. Or
is it my SOGo configuration after all? Where are your two cents? ;-)
From: stefan_mayer...@hotmail.com
To: users@sogo.nu
Date: Fri, 8 Mar 2013 14:28:38 +0100
Subject: [SOGo] login form's action is "//connect" and cookie path is
"/connect/"
Whenever I load the login page I have to manually edit the source using
Firebug in order to send off the form: the form's action is set to
"//connect" which, of course, does not work; it does, however, when I
modify it to "/connect". Any idea why this happens? I looked for a
hostname setting in sogo's GNUstep defaults, but I couldn't find one. Is this
in some way related to the headers x-webobjects-server-name or
x-webobjects-server-url? This is how they are currently set in my nginx config:
proxy_set_header Host $host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $host;
proxy_set_header x-webobjects-server-url $scheme://$host;
Another, probably related, issue is that the path of the cookies SOGo is using
is set to "/connect/", which does not work (my installation is in root). My
current workaround is
proxy_cookie_path /connect/ /;
Thanks for your help!
stefan
--
users@sogo.nu
https://inverse.ca/sogo/lists
