mrubinsk Fri, 25 Oct 2013 16:51:32 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 214
Change log: Expand on the Autodiscover setup.
@@ -41,17 +41,43 @@
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
</code>
None of these issues have been reported using lighttpd/fastcgi.
-In order for the Autodiscovery service to work, you should also
create an alias/rewrite rule for the URL
/autodiscover/autodiscover.xml to horde/rpc.php as well:
++++ 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.
+
+The easiest example is when Horde is running on the same domain, with
NO subdomain as the email address domain. Example, for
[email protected] and Horde is reachable at https://example.com/horde.
For this, you simply create an Alias pointing
/autodiscover/autodiscover.xml to /rpc.php. Note that the
documentation specifies different case for the URL in different parts.
You should allow the following URLs to be redirected:
<code>
Alias /autodiscover/autodiscover.xml /var/www/horde/rpc.php
+Alias /Autodiscover/Autodiscover.xml /var/www/horde/rpc.php
+Alias /AutoDiscover/AutoDiscover.xml /var/www/horde/rpc.php
</code>
-Note that the Autodiscovery service attempts to contact domain used
in the email address, not necessarily the sub domain that Horde is
installed at so e.g., if your Horde install is at
https://horde.example.com but your users use [email protected] then you
will need to redirect requests for
https://example.com/autodiscover/autodiscover.xml to
https://horde.example.com/autodisocover/autodiscover.xml:
+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.
+
+If, the ActiveSync client, fails to find an acceptable autodiscover
response at https://example.com will then send a request to
http://autodiscover.example.com. Note that this is NOT over SSL. This
request MUST respond with a 302 redirect to a SSL endpoint that will
answer the autodiscover request:
+
+<code>
+<VirtualHost *:80>
+ ServerName autodiscover.example.com
+ DocumentRoot /var/www/html
+ RedirectMatch 302 (?i)/autodiscover/autodiscover.xml
https://mail.example.com/autodiscover/autodiscover.xml
+</VirtualHost>
+
+# Obviously, you can't use a wildcard 443 here, but you get the
idea...basically you
+# need to set these Alias entries for
https://mail.example.com/autodiscover/autodiscover.xml
+<VirtualHost *:443>
+ ServerName mail.example.com
+ Alias /autodiscover/autodiscover.xml /var/www/html/groupware/rpc.php
+ Alias /Autodiscover/Autodiscover.xml /var/www/html/groupware/rpc.php
+ Alias /AutoDiscover/AutoDiscover.xml /var/www/html/groupware/rpc.php
+
+ ## Rest of config....
+</VirtualHost>
+</code>
-For lighttpd:
++++ Basic example for lighttpd:
<code>
$HTTP["host"] =~ "(^|www\.)example\.com$" {
url.redirect = ("^/(?i)autodiscover/autodiscover.xml$" =>
"https://horde.example.com/autodiscover/autodiscover.xml";)
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
