Outlook Anywhere

Outlook Anywhere or short OAW can be configured to use RPC over HTTP. Microsoft abuses the HTTP protocols content length by setting it to 1GB and streaming RPC over it. OAW then opens a downstream by sending a RPC_IN_DATA request to the OAW server which sends a response with a length of 1GB. OAW also opens an upstream by sending a RPC_OUT_DATA post request with a body length of 1GB. After setting up these to connections, OAW sends its commands and data over this two connections. The proxy has to deliver every chunk of RPC data no matter how small without buffering or delaying directly from the client to the backend or vice versa.

All buffering filters like rewrite and validation filter must not be mapped to the OAW path.

You have to increase the request body limit to 1073741824 in the navajo.xml by adjusting the server attribute LimitRequestBody. The default request body limit set by apache is 512000.

In your connector servlet mapped to the OAW path, set KeepAlive and Poll to true.

In addition, allow the methods RPC_IN_DATA and RPC_OUT_DATA in the navajo.xml by adjusting the Context attribute allowedMethods accordingly.