Enables the Object Prefetch Table, which stores HTTP object prefetches from HTTP GET requests for cascading style sheets, static images, and Java scripts in the Object Prefetch Table. When the browser performs If-Modified-Since (IMS) checks for stored content or sends regular HTTP requests, the client-side SteelHead responds to these IMS checks and HTTP requests, reducing round trips across the WAN.

Enables Parse and Prefetch, which parses the base HTML page received from the server and prefetches any embedded objects to the client-side SteelHead. This option complements URL Learning by handling dynamically generated pages and URLs that include state information. When the browser requests an embedded object, the SteelHead serves the request from the prefetched results, eliminating the round-trip delay to the server.

The prefetched objects contained in the base HTML page can be images, style sheets, or any Java scripts associated with the base page and located on the same host as the base URL.

Parse and Prefetch requires cookies. If the application does not use cookies, you can insert one using the insert-cookie option.

Enables URL Learning, which learns associations between a base URL request and a follow-on request. Stores information about which URLs have been requested and which URLs have generated a 200 OK response from the server. This option fetches the URLs embedded in style sheets or any JavaScript associated with the base page and located on the same host as the base URL.

URL Learning works best with content that is not dynamic and does not contain session-specific information. URL Learning is enabled by default.

Your system must support cookies and persistent connections to benefit from URL Learning. If your system has cookies turned off and depends on URL rewriting for HTTP state management, or is using HTTP v1.0 (with no keep-alives), you can force the use of cookies by using the Add Cookie option and force the use of persistent connections using the Insert Keep Alive option.

Allows an unauthenticated connection to serve prefetched objects, as long as the connection belongs to a session whose base connection is already authenticated.

This option is most effective when the web server is configured to use per-connection NTLM or Kerberos authentication.

Enables the client-side SteelHead to split Silverlight smooth streaming, Adobe Flash HTTP dynamic streams, and Apple HTTP Live Streaming (HLS).

This control includes support for Microsoft Silverlight video and Silverlight extensions support on Internet Information Server (IIS) version 7.5 installed on Windows Server 2008 R2.

To split Adobe Flash streams, you must set up the video origin server before enabling this control. For details, see the SteelHead Deployment Guide - Protocols.

Removes all credentials from the request on an already authenticated connection. This works around Internet Explorer behavior that reauthorizes connections that have been previously authorized.

This option is most effective when the web server is configured to use per-connection NTLM authentication.

Prevents a WAN round trip by issuing the first 401 containing the realm choices from the client-side SteelHead.

Riverbed recommends enabling strip-auth-hdr along with this option.

This option is most effective when the web server is configured to use per-connection NTLM authentication or per-request Kerberos authentication.

Forces NTLM In the case of negotiated Kerberos and NTLM authentication. Kerberos is less efficient over the WAN because the client must contact the domain controller to answer the server authentication challenge and tends to be employed on a per-request basis.

Riverbed recommends enabling strip-auth-hdr with this option.

This setting is disabled by default.

Removes the accept-encoding lines from the HTTP compression header. An accept-encoding directive compresses content rather than using raw HTML. Enabling this option improves the performance of the SteelHead data-reduction algorithms.

Specify yes to enable this feature; specify no to disable it.

This setting is enabled by default.

Adds a cookie to HTTP applications that do not already have one. HTTP applications frequently use cookies to monitor sessions. The SteelHead uses cookies to distinguish one user session from another. If an HTTP application does not use cookies, the client SteelHead inserts one so that it can track requests from the same client. By default, this setting is disabled.

Uses the same TCP connection to send and receive multiple HTTP requests and responses, as opposed to opening new ones for every single request and response.

Enable this option when using the URL Learning or Parse and Prefetch features with HTTP v1.0 or HTTP v1.1 applications using the Connection Close method.

This setting is disabled by default.

Enables or disables SharePoint Front Page Server Extensions Protocol (FPSE) on a subnet or hostname.

RiOS 8.5 caches and responds locally to all FPSE requests to save at least five round trips per request, resulting in performance improvements. SSL connections and files smaller than 5 MB can experience significant performance improvements.

This setting is disabled by default.

Enables or disables SharePoint Web-based Distributed Authoring and Versioning (WebDAV) on a subnet or hostname.

WebDAV is an open-standard extension to the HTTP 1.1 protocol that enables file management on remote web servers. WebDAV is used by the WebDAV redirector, Web Folders, SMS/SCCM, and many other Microsoft components.

SharePoint clients typically issue a Depth 0 request, then subsequently issue a Depth 1 request. RiOS fetches the Depth 1 response in place of the Depth 0 response and then serves subsequent Depth 1 and Depth 0 requests on collection/internal members locally. Serving requests locally saves multiple round trips and makes browsing the SharePoint file repository more responsive.

This setting is disabled by default.

Enables or disables SharePoint File Synchronization via SOAP over HTTP (FSSHTTP) on a subnet or hostname.

This setting is disabled by default.