[commits] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Mon, 08 Apr 2013 15:07:16 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  173
Change log:  This is *not* correct, but some clients send a broken URL.

@@ -46,21 +46,23 @@
  <code>
  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 user at example.com then you  
will need to redirect requests for  
https://example.com/AutoDiscover/AutoDiscover.xml to  
https://horde.example.com/AutoDisocover/AutoDiscover.xml:
+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 user at example.com then you  
will need to redirect requests for  
https://example.com/autodiscover/autodiscover.xml to  
https://horde.example.com/autodisocover/autodiscover.xml:

  For lighttpd:

  <code>
  $HTTP["host"] =~ "(^|www\.)example\.com$" {
-    url.redirect = ("^/(?i)AutoDiscover/AutoDiscover.xml$" =>  
"https://horde.example.com/autodiscover/autodiscover.xml")
+    url.redirect = ("^/(?i)autodiscover/autodiscover.xml$" =>  
"https://horde.example.com/autodiscover/autodiscover.xml")
  }

  alias.url = ("/Microsoft-Server-ActiveSync" => "/var/www/horde/rpc.php",
               "/autodiscover/autodiscover.xml" => /var/www/horde/rpc.php");
  </code>
  Note that Autodiscover support is VERY flaky in most clients that we  
have tested.
+
+It should also be noted that the protocol documentation explicitly  
lists the autodiscover url as all lowercase, some clients actually  
request it as //AutoDiscover/AutoDiscover.xml// so if you are having  
problems, you should adjust your alias/rewrite rules accordingly.

  ++ Application Configuration
  No additional steps are normally necessary for synchronization of  
the supported applications. However, each application that supports  
synchronization also has a user preference to determine which shares  
will be synchronized. For example, in Kronolith the user's default  
calendar is *always* synchronized, but the user can choose to add any  
additional calendars he/she owns. Whenever the user changes one of  
these settings, the device is always automatically re-paired with the  
server to pick up the change.