For posterity, A working CardDAV Apache VirtualHost config is as follows. Replace your.server.com with your fqdn (ignore the SSL stuff if you don't want that).
#Below for CardDAV access <VirtualHost your.server.com:8843> SSLEngine on SSLCertificateFile /etc/ssl/your_server_com.crt SSLCertificateKeyFile /etc/ssl/your_server_com.key ErrorLog /var/log/apache2/error.log ProxyRequests Off SetEnv proxy-nokeepalive 1 ProxyPreserveHost On ProxyPassInterpolateEnv On ProxyPass /SOGo/dav/ http://127.0.0.1:20000/SOGo/dav/ interpolate ProxyPass / http://127.0.0.1:20000/SOGo/dav/ interpolate <Proxy http://127.0.0.1:20000> ## adjust the following to your configuration RequestHeader set "x-webobjects-server-port" "8843" RequestHeader set "x-webobjects-server-name" "your.server.com" RequestHeader set "x-webobjects-server-url" "https://your.server.com"; ## 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" "127.0.0.1" Order allow,deny Allow from all </Proxy> </VirtualHost> Thanks again to Inverse for their continued work on SOGo. Regards, Mark On Mon, Aug 23, 2010 at 10:43:26AM +0100, Mark Adams wrote: > Unfortunately it's still not right. I've found that with it set as I > note below, new phones cannot verify. If you change it to > > ProxyPass / http://127.0.0.1:[port]/SOGo/dav/ as specifed in Wolfgangs > howto, then phones can verify but can not sync anything. If you change > it back to what I have below (without /SOGo/dav/) after verifying then > the phones will start syncing events. > > Any ideas Inverse? > > On Fri, Aug 20, 2010 at 10:03:58PM +0100, Mark Adams wrote: > > Hi Ryan, > > > > What Wolfgang says is right, except for me the 2nd ProxyPass had to be > > the following; (no SOGo/dav/ at the end) > > > > ProxyPass / http://127.0.0.1:[port]/ interpolate > > > > If you need the full config let me know and i'll send through to you. > > > > Cheers, > > Mark > > > > On Fri, Aug 20, 2010 at 04:01:18PM -0400, Wolfgang Sourdeau wrote: > > > Hi Ryan, > > > > > > > > > You need a VirtualHost section with exactly the same directives as in > > > your original SOGo configuration except 3 things: > > > 1) it must listen on 8800 (clear) or 8843 (ssl) > > > 2) you need both ProxyPass directives instead of one: > > > > > > ProxyPass /SOGo/ http://127.0.0.1:[port]/SOGo/ interpolate > > > ProxyPass / http://127.0.0.1:[port]/SOGo/dav/ interpolate > > > > > > 3) the Proxy subsection must also be modified to reflect the port you > > > have chosen: > > > > > > For port 8843 you'd have something like this: > > > > > > <Proxy http://127.0.0.1:[port]> > > > RequestHeader set "x-webobjects-server-port" "8843" > > > RequestHeader set "x-webobjects-server-name" "mygoodcompany.com:8843" > > > RequestHeader set "x-webobjects-server-url" > > > "https://mygoodcompany.com:8843"; > > > RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0" > > > RequestHeader set "x-webobjects-remote-host" "127.0.0.1" > > > > > > AddDefaultCharset UTF-8 > > > </Proxy> > > > > > > Note that Apache will likely issue a warning about the redefinition of > > > the http://127.0.0.1:[port] proxy but you can safely ignore it. > > > -- > > > Wolfgang Sourdeau :: +1 (514) 447-4918 ext. 125 :: > > > wsourd...@inverse.ca > > > Inverse inc. Leaders behind SOGo (sogo.nu) and PacketFence > > > (www.packetfence.org) > > > > > -- > > > users@sogo.nu > > > https://inverse.ca/sogo/lists > > > -- > > users@sogo.nu > > https://inverse.ca/sogo/lists > -- > users@sogo.nu > https://inverse.ca/sogo/lists
-- users@sogo.nu https://inverse.ca/sogo/lists
