Seems very elegant solution even I am not very familiar with RewriteEngine.
If this is something that works for every case, I would say that putting your proxy section in standard SOGo package would allow SOGo install without any change of this file later (as one of the install steps). Maybe SOGo team could consider this for future releases.
Thanks, Igor Romain LE DISEZ wrote, On 30/10/2012 18:32:
Here is my proxy section. It works for any domain, any ports, HTTP or HTTPS. <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:%{SOGO_SERVER_PORT}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> Greetings.
-- [email protected] https://inverse.ca/sogo/lists
