Sources of Latency > About Caching > Reverse Proxy >
Forward Proxy > Static vs. Dynamic Content > Deciding What to Cache

Forward Proxy

Warp software can be configured as a forward proxy as well.  In forward proxy mode, data is cached before it is requested, rather than after, according to administrative directives.  In this way, content can be ‘pre-positioned’ in the cache, so that requests for the pre-positioned content can be fulfilled without the need to burden origin servers. 

Content pre-positioning is an extremely useful capability for geographically remote locations that are otherwise constrained by network bandwidth connections.  Network administrators can preposition popular content to avoid excessive bandwidth utilization and network congestion that would otherwise ensue.  Large files, such as rich media, are ideal candidates for forward proxy treatment.

Omneo ProxyCache in Forward Proxy Mode

In the diagram above, forward proxy operation of Omneo ProxyCache is illustrated as follows.  Content from the origin server is moved into the cache prior to any requests for it from the user community (1.)  Any subsequent requests for prepositioned content are fulfilled directly out of the cache (2,5).  Requests for content that has not been cached are passed on by Omneo ProxyCache for fulfillment by the origin server in the conventional fashion (2,3,4,5).  If Omneo ProxyCache has also been configured to function as a reverse proxy, it will cache requested content locally before delivering it to the requesting user, as described above (3,4).