[commits] [Wiki] changed: ActiveSync

[Wiki Guest]

guest [46.166.186.220]  Tue, 19 May 2015 14:59:10 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  279
Change log:  The ProxyPassMatch syntax has changed

@@ -47,9 +47,9 @@
  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
+ProxyPassMatch ^/Microsoft-Server-ActiveSync$  
unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1
  </code>
  // Note: // Sockets are only available from Apache 2.4.8 or if the  
appropriate patch has been applied. In all other case, use a tcp  
connection.
  // Note: // If setting // !ProxyErrorOverride On // then when  
testing the !ActiveSync endpoint via a browser you may not see the  
expected activesync error message - as it would be replaced by the  
overridden Apache error message.

@@ -69,11 +69,11 @@
  </code>

  For Apache + PHP-FPM using mod_proxy_fcgi
  <code>
-ProxyPassMatch ^/autodiscover/autodiscover.xml$  
fcgi://socket=%2fusr%2flocal%2fphp54%2fsockets%2fhorde.sock/var/www/html/horde/rpc.php$1
-ProxyPassMatch ^/Autodiscover/Autodiscover.xml$  
fcgi://socket=%2fusr%2flocal%2fphp54%2fsockets%2fhorde.sock/var/www/html/horde/rpc.php$1
-ProxyPassMatch ^/AutoDiscover/AutoDiscover.xml$  
fcgi://socket=%2fusr%2flocal%2fphp54%2fsockets%2fhorde.sock/var/www/html/horde/rpc.php$1
+ProxyPassMatch ^/autodiscover/autodiscover.xml$  
unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1
+ProxyPassMatch ^/Autodiscover/Autodiscover.xml$  
unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1
+ProxyPassMatch ^/AutoDiscover/AutoDiscover.xml$  
unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1
  </code>

  A more common example is when Horde is running on something like  
mail.example.com while the email addresses are simply @example.com.  
For this, there are two options. First, if example.com is an existing  
site, already runs over HTTPS and is on the same physical server as  
mail.example.com, you could simply use the Alias example above in the  
configuration for the example.com site. Note again, this MUST ALL BE  
OVER SSL.