On 12/03/12 19:04, Michael Gratton wrote:
There is no SOGo log entry, because on clicking the Save button for the
event the browser tries to submit to localhost rather than to the SOGo
installation's host.

I.e. The browser sends the request to:[snip]

Rather than:

Instead of :

        RequestHeader set "x-webobjects-remote-host" ""


RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST


        BalancerMember retry=1 max=1 timeout=120
        BalancerMember retry=1 max=1 timeout=120

is most likely wrong. I don't recall if v1.3.6 had the master process code which is dispatching requests to child processes but you could easily verify this by checking if port 20001 is open. If not, the following Apache configuration might suit you better and mod_proxy_balancer is no longer needed:

ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On

ProxyPass /SOGo retry=0

  RequestHeader set "x-webobjects-server-port" "80"
  RequestHeader set "x-webobjects-server-name" "collab.internal.xyz.com"
RequestHeader set "x-webobjects-server-url" "http://collab.internal.xyz.com";

  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

Ludovic Marcotte
+1.514.755.3630  ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 


Reply via email to