An other option. Replace the proxy section with this one :
<Proxy http://127.0.0.1:20000/SOGo>
RewriteEngine On
RewriteBase /
RewriteRule .* -
[E=SOGO_HTTP_SCHEME:http,E=SOGO_HTTP_HOST:%{HTTP_HOST},E=SOGO_SERVER_PORT:%{SERVER_PORT},NE]
RewriteCond %{HTTPS} =on
RewriteRule .* - [E=SOGO_HTTP_SCHEME:https,NE]
## adjust the following to your configuration
RequestHeader set "x-webobjects-server-port" "%{SOGO_SERVER_PORT}e"
RequestHeader set "x-webobjects-server-name" "%{SOGO_HTTP_HOST}e"
RequestHeader set "x-webobjects-server-url"
"%{SOGO_HTTP_SCHEME}e://%{SOGO_HTTP_HOST}e"
## When using proxy-side autentication, you need to uncomment and
## adjust the following line:
# RequestHeader set "x-webobjects-remote-user" "%{REMOTE_USER}e"
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST
AddDefaultCharset UTF-8
Order allow,deny
Allow from all
</Proxy>
This configuration will work for every host and every port you use. I use it as
a standard configuration for small deployment or multi-domains deployment.
Le Mardi 20 Décembre 2011 21:11 CET, Paul van der Vlis <[email protected]> a
écrit:
> Op 20-12-11 20:51, "Daniel Müller" schreef:
> > I myself tried the same wioth SOGo. And it did not work as it should.
> > The problem I think is that SOGo itself has a redirected rule in apaches
> > sogo.conf. And ist is difficult to redirect this rule again so it can fit
> > with the local network too.
>
> I am using a setup what I've described here: http://wiki.debian.org/SOGo
>
> I can switch between port 443 and port 80. I don't use sogo.conf, see my
> apache setup at the end of the page.
>
> With regards,
> Paul van der Vlis.
>
>
> --
> Paul van der Vlis Linux systeembeheer Groningen
> http://www.vandervlis.nl
>
> --
> [email protected]
> https://inverse.ca/sogo/lists
--
Romain LE DISEZ
--
[email protected]
https://inverse.ca/sogo/lists
