Changes the default value of the server table. This option is used for all traffic if no specific match is found.

Specifies one of the following networks for the HTTP server subnet:

Specifies a specific hostname.

Specifies all hostnames.

Enables (yes) or disables (no) 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.

The Object Prefetch Table is disabled by default.

Enables (yes) or disables (no) the Parse-and-Prefetch option, 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.

Parse-and-Prefetch is enabled by default.

Enables (yes) or disables (no) URL Learning, which learns associations between a base URL request and a follow-on request. This option 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 your system is using HTTP v1.0 (with no keep-alives), you can force the use of cookies by using the insert-cookie option and force the use of persistent connections using the insrt-keep-aliv option.

Allows (yes) or disallows (no) 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.

Adds (yes) credentials to the request on an already authenticated connection or removes (no) all credentials from the request on an already authenticated connection. This works around Internet Explorer behavior that re-authorizes connections that have been previously authorized.

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

Enables (yes) or disables (no) gratuitous-401 settings. When set to Yes, the system 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.

In the case of negotiated Kerberos and NTLM authentication, requires (yes) NTLM or does not (no) require NTLM. Allows use of Kerberos. However, 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 option is disabled by default.

Enables (yes) strip compression or disables (no) strip compression.

Strip compression 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.

This option is enabled by default.

Enables (yes) the ability to add cookies to HTTP applications if needed or disables (no) this ability.

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.

This option is disabled by default.

Enables (yes) the keep alive function or disables (no) this function.

When this function enabled, the system 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 option is disabled by default.

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

This option is case sensitive and is disabled by default.

Enables (yes) or disables (no) 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 option is case sensitive and is disabled by default.

FSSHTTP

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

This option is case sensitive and is enabled by default.