




Content Caching is an application delivery performance enhancing feature that has traditionally only been found on dedicated devices or top end application delivery controllers.
The basic principle of a content cache is to store common responses to web requests such as images in an internal ‘cache’ and only send unique requests back to the to the web servers. This means that the content cache will respond to the end user on behalf of the web server. The benefit is that you will need less web servers because the load balancer cache is doing much of the work. In addition to this, the user will tend to get a better response time due to a reduction in back end traffic load and quicker transit times.
Supporting multiple variants of the same content allowsthe jetNEXUS Enterprise Traffic Manager to cache even dynamic content where this is desirable. For example, if you have different content for local users and remote users, or if you embed the username of a logged-in user into each page, you can cache these customized pages and ensure that each user receives the correct version from the content cache.
