An overview of the Cache Redirection feature on the system and how it works.
Summary
The cache redirection feature supports HTTP and TCP-based protocols. For HTTP protocols, three modes of redirection are supported: origin, cache, and policy (that is, either traffic is forwarded to the origin server, or to the cache server, or traffic is redirected based on the policies configured on the system.) For TCP-based protocols, only two modes of redirection are supported, origin and cache.
The following entity diagram illustrates a typical cache redirection configuration. 
Cache redirection entity model
As shown in this figure, to configure cache redirection, you must define a cache redirection vserver, a load balancing vserver, services, and cache redirection policies.
The cache redirection policies enable the system to identify cacheable and non-cacheable requests for every HTTP transaction by parsing the URL (suffix, prefix, and query string tokens) and the HTTP header (specific header, cache-control header, and method). The cache redirection policies are bound to the cache redirection vserver. Cache redirection is handled between two vservers. The cache redirection vserver routes the cacheable client requests to a target vserver, which is the load balancing vserver in this case. The load balancing vserver directs the cacheable client requests to the cache services that represent the cache servers. Non-cacheable client requests or cache misses are sent to the origin server..
More Information
