Microsoft IIS 8.0 supported   Relay Server can now be set up with Microsoft IIS 8.0. See Deploying the Relay Server components to Microsoft IIS 7.0, 7.5, or 8.0.

Quick setup for Microsoft IIS 7.0, 7.5, and 8.0   An interactive quick setup feature, rs-setup.bat, is provided as an alternative to the manual procedure. rs-setup.bat is located in the %SQLANY16%/RelayServer/IIS/quicksetup_iis7or8 directory and performs the following tasks:

See Deploying the Relay Server components to Microsoft IIS 6.0 on Windows Server 2003 and Deploying the Relay Server components to Microsoft IIS 7.0, 7.5, or 8.0.

Apache 2.4 supported   Apache 2.4 is now supported.

See Deploying the Relay Server components to Apache on Linux.

Quick setup for Apache on Linux   The quick setup feature performs the following tasks:

See Deploying the Relay Server components to Apache on Linux.

Improved troubleshooting for Outbound Enabler   Outbound Enabler error messages have been improved with error codes and more detailed problem resolution suggestions to assist in troubleshooting.

Improved server response flow control   On occasion, shared memory resources can become exhausted due to issues with excessive buffering of server responses, which can include large numbers of clients, slow-reading clients, or large HTTP responses. To improve memory usage, Relay Server provides a new configuration option, max_client_buffer = memory size, allowing you to specify a limit on the memory buffer size for each client. The default value is 1 MB. The maximum value is 4 GB. See Backend farm section.

Renew overlapped cookie   In the case where a client is sharing an overlapping standard cookie across multiple concurrent connections, timeout errors can occur. This issue will appear in the Relay Server log. When renew_overlapped_cookie is set on, Relay Server detects the cookie overlap for the farm that has this property explicitly turned on and renews the overlapping cookie by creating a new affinity binding. See Backend farm section.

Improved proxy support using automatic passthrough   Proxies use HTTPS passthrough using a CONNECT request to establish a non-SSL-terminating tunnel. This new feature allows data streaming on Outbound Enabler connections to the Relay Server through buffering proxies.

up_pad_size setting (rs.config options section)   This setting inserts a pad of maximum transmission unit (MTU) size to improve latency when sparse numbers of small requests are being uploaded via the RSOE channel. Latency for the Outbound Enabler is also improved for server responses. See Options section.

Remote administration of the Relay Server log file   Remote administration of the Relay Server log file is supported through the AdminChannel class in rstool.jar, providing:

• Remote configuration update and retrieval
• Remote Relay Server log extraction
• Local Outbound Enabler log extraction
• Relay Server log archiving

See Remote administration of the Relay Server log file.