[commits] [Wiki] changed: ActiveSync

[Wiki Guest]

guest [84.227.86.7]  Thu, 30 Jan 2014 22:58:38 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  240
Change log:  Added timout variable for mod_proxy_fcgi

@@ -31,14 +31,8 @@
  You will need to configure your webserver to redirect the URL  
/Microsoft-Server-ActiveSync to your horde/rpc.php file. How you do  
this depends on your webserver and it's configuration. For Apache,  
something like:
  <code>
  Alias /Microsoft-Server-ActiveSync /var/www/horde/rpc.php
  </code>
-
-For Apache + PHP-FPM using mod_proxy_fcgi
-<code>
-ProxyPassMatch ^/Microsoft-Server-ActiveSync$  
fcgi://socket=%2fusr%2flocal%2fphp54%2fsockets%2fhorde.sock/var/www/html/horde/rpc.php$1
-</code>
-
  // Note: // It has been reported that when running PHP via mod_fcgid  
on Apache that the Alias directive will not pass the correct URL to  
the fcgid-script handler. This can be worked around by using a  
!RewriteRule instead (adapted from  
http://maurus.net/weblog/2010/10/26/running-z-push-1-4-2-with-apache-and-fastcgifcgid/):
  <code>
      RewriteEngine On
      RewriteRule ^/Microsoft-Server-ActiveSync /horde/rpc.php [PT,L,QSA]
@@ -49,8 +43,15 @@
  RewriteRule .* - [E=HTTP_X_MS_POLICYKEY:%{HTTP:X-Ms-Policykey}]
  RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  </code>
  None of these issues have been reported using lighttpd/fastcgi or  
Apache+mod_fastcgi+php-fpm.
+
+For Apache + PHP-FPM using mod_proxy_fcgi
+<code>
+ProxyPassMatch ^/Microsoft-Server-ActiveSync$  
fcgi://socket=%2fusr%2flocal%2fphp54%2fsockets%2fhorde.sock/var/www/html/horde/rpc.php$1
+</code>
+Since Horde !ActiveSync connections are held open for a period of  
time up to 3540 seconds (depending on client and  
$conf[activesync][ping][heartbeatmax] setting, if using a proxy server  
you need to ensure it does not time out before the request is  
complete. Add this to your virtualhost
+ProxyTimeout 5400

  +++ Autodiscover

  In order for the Autodiscovery service to work, a request to  
/autodiscover/autodiscover.xml needs to reach rpc.php. How it does  
this depends on your specific server setup. Below are a few examples  
to point you in the right direction. Note that for autodiscovery to  
work, the final endpoint MUST be over SSL. Autodiscover requests will  
NOT work without a valid SSL certificate.