Using a Reverse Proxy for OData Applications

Requirements for third party reverse proxies for use with SAP Mobile Platform.

The reverse proxy must be a straight pass-though proxy server. Ensure the reverse proxy meets these requirements:

Does not change the content encoding of the requests or responses. Chunked transfer encoding is the required data transfer mechanism. Content-length encoding is not supported.
Does not remove any HTTP headers.
The timeout period (if any) must be greater than the timeout used by the clients.
The resulting URL that is passed to the SAP Mobile Platform must be http://HostName:port.

The OData application needs to communicate to the message server port. The configuration policies are:

Map the root context of http://reverseProxy:5001 to http://supServer:5001. Set connection properties just as you would to directly connect to SAP Mobile Server.
Map the "/smp/message" context of http://reverseProxy:8080 to http://supServer:5001. The OData application needs to add the "/smp/message" as URL suffix for connection properties during registration.