Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
This page has the following components:
Maximum client buffer size Specify the amount of memory, per client request, that the Relay Server can use for downloads (per request). The change takes effect immediately and the Relay Server does not need to be restarted. The default value is 1 MB and the maximum value is 4 GB.
Client-Server Affinity Specifies the type of backend server. Select SQL Anywhere for SQL Anywhere web services using standalone Outbound Enablers. Select MobiLink for either a MobiLink server with an embedded Outbound Enabler or MobiLink HTTP server with standalone Outbound Enablers. Select Custom for setting advanced affinity options tailored for the backend servers in your HTTP environment.
Active cookie Specifies whether the Relay Server is going to inject a standard HTTP cookie to maintain client-server affinity.
If selected, the Relay Server injects a standard HTTP set-cookie command with a proprietary cookie name in the response to maintain client-server affinity.
If the checkbox is cleared, then no standard HTTP set-cookie command is injected into the response. The client-server affinity is either maintained by active header or no affinity is required by your application.
Active header Specifies whether or not the Relay Server is going to inject a proprietary header to maintain client-server affinity.
If selected, the Relay Server injects a proprietary header in the response to maintain client-server affinity. This is useful in cases where intermediaries tamper with active cookies. Active header works only if the client application supports the Relay Server active header reflection. Web browsers in general do not support Relay Server active header.
If the checkbox is cleared, then no proprietary header is injected into the response. The client-server affinity is either maintained by active cookie or no affinity is required by your application. Clear the checkbox to cut down on traffic volume if the backend farm is serving only browser applications, or if the active cookie is working well for all the clients of this backend farm.
Renew Overlapped Cookie In the case where a client is sharing a standard cookie across multiple concurrent connections, timeout errors can occur. This issue appears in the Relay Server log. Turning Renew Overlapped Cookie on can reduce the number of dropped connections.
With Renew Overlapped Cookie turned on, Relay Server detects the cookie overlap for this farm and renews the overlapping cookie by creating a new affinity binding. The request with the renewal is still routed to the same backend server, but not the same backend connection as the ongoing request that it overlaps with. A new backend connection is created instead.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|