[commits] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Tue, 11 Jun 2013 14:13:51 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  196
Change log:  Tweaks

@@ -64,27 +64,23 @@
  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.

  +++ Setting up Horde !ActiveSync behind a Reverse Proxy Server

-Horde !ActiveSync connections are held open for a period of time up  
to $conf[activesync][ping][heartbeatmax] (max 3540 seconds). This can  
cause issues with proxy servers timing out on connections, resulting  
in errors like this in your proxy server's web server log:
+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. Failure to do this will result in errors like this in your  
proxy server's web server log:

  <code>
  [Mon Jun 10 22:24:56 2013] [error] [client 101.169.127.248]  
(70007)The timeout specified has expired: proxy: error reading status  
line from remote server 192.168.1.230
  [Mon Jun 10 22:24:56 2013] [error] [client 101.169.127.248] proxy:  
Error reading from remote server returned by  
/Microsoft-Server-ActiveSync
  </code>

-You need to ensure that your proxy server's configuration for the  
proxy allows for this.
-
-For an Apache proxy, my proxy server's timeout configuration is this:
+For an Apache proxy:

  <code>
-  ProxyPass        / https://192.168.1.230/ connectiontimeout=600  
timeout=3000
+  ProxyPass        / https://192.168.1.230/ connectiontimeout=600  
timeout=4000
    ProxyPassReverse / https://192.168.1.230/
  </code>

-That allows for up to 600 seconds for a connection to be established  
(should cover ALL possibilities!) and then holds that connection open  
for up to 3000 seconds. My $conf[activesync][ping][heartbeatmax] is  
2700 seconds.
-
-This configuration completely got rid of remote server errors on my  
proxy server, and also slightly reduced chat between the devices and  
Horde, which should increase battery life.
+That allows for up to 600 seconds for a connection to be established  
(should cover ALL possibilities) and then holds that connection open  
for up to 4000 seconds. This should be adjusted for you specific  
needs/environment.

  +++ Horde

  You should make sure that the max_execution time is either set to 0  
or at least twice the maximum heartbeat interval. This can be set in  
Horde's general configuration tab.