mrubinsk Tue, 11 Jun 2013 14:07:22 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 195
Change log: Move this to the setup section
@@ -62,8 +62,30 @@
</code>
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:
+
+<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:
+
+<code>
+ ProxyPass / https://192.168.1.230/ connectiontimeout=600
timeout=3000
+ 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.
+
+++ 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.
@@ -173,30 +195,8 @@
+++ Issues/Workarounds
For some reason, Outlook 2013 doesn't use EAS to provide Free/Busy
lookup, even though the version of the EAS protocol it uses supports
it. If you want Outlook to be able to lookup Free/Busy information
using Horde/Kronolith you need to provide it with the Free/Busy URL.
Under //File -> Options -> Calendar Options// select the "Free/Busy
Options" button. Enter Kronolith's Free/Busy URL:
http://example.com/horde/kronolith/fb.php?u=%NAME%. The %NAME% string
will be replaced by the user portion of the SMTP mailing address used
in the meeting request.
-
-++ 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:
-
-<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:
-
-<code>
- ProxyPass / https://192.168.1.230/ connectiontimeout=600
timeout=3000
- 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.
++ What to do if you have problems (or How to help us help you)
**First off, you should check the list of
((ActiveSync/KnownIssues|known issues)) to see if your problem is
expected or not**. You can also check the Horde bug tracker to see if
your issue has been reported already.
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
