LupusNobilis
/
sogo
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Monotone-Parent: 24ad1ea4c7c45424c62bc468e315d77139691089 

Monotone-Revision: 4eb36e8b2021cf9b64520bb8434bff43f5716ee9

Monotone-Author: wsourdeau@inverse.ca
Monotone-Date: 2009-09-25T15:22:50
Monotone-Branch: ca.inverse.sogo
maint-2.0.2
Wolfgang Sourdeau 2009-09-25 15:22:50 +00:00
parent f82236c4a1
commit a8a1f20f35
2 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Apache/SOGo-debian.conf
View File

@ -29,6 +29,18 @@ AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*) \
/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2
<Proxy balancer://sogocluster>
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
## adjust the following to your configuration
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "yourhostname"
RequestHeader set "x-webobjects-server-url" "https://yourhostname"
## When using proxy-side autentication, you need to uncomment and
## adjust the following line:
# RequestHeader set "x-webobjects-remote-user" "%{REMOTE_USER}e"
BalancerMember http://127.0.0.1:20000 retry=1 max=1 timeout=120
# If you enable those, don't forget the enable the spawning of multiple SOGo
# processes. With Redhat-based distributions, this is done by setting the

2
Apache/SOGo.conf
View File

@ -51,7 +51,7 @@ ProxyPass /SOGo balancer://sogocluster/SOGo
<Proxy balancer://sogocluster>
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-addr" "127.0.0.1"
RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
## adjust the following to your configuration
RequestHeader set "x-webobjects-server-port" "443"