Support

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching
Web Proxy Caching
 
Help | Content Gateway | Version 7.7.3
Web proxy caching stores copies of frequently accessed Web objects (such as documents, images, and articles) close to users and serves this information to them. Internet users get their information faster, and Internet bandwidth is freed for other tasks.
Internet users direct their requests to Web servers all over the Internet. For a caching server to serve these requests, it must act as a Web proxy server. A Web proxy server receives user requests for Web objects and either serves the requests or forwards them to the origin server (the Web server that contains the original copy of the requested information).
Content Gateway supports both transparent proxy deployment, in which the user's client software (typically a browser) is unaware that it is communicating with a proxy, and explicit proxy deployment, in which the user's client software is configured to send requests directly to the proxy.
Cache requests
 
Related topics:
*
Ensuring cached object freshness
*
Scheduling updates to local cache content
*
Pinning content in the cache
*
To cache or not to cache?
*
Caching HTTP objects
*
Forcing object caching
*
Caching HTTP alternates
*
Caching FTP objects
The following overview illustrates how Content Gateway serves a user request.
1.
Content Gateway receives a user request for a Web object.
2.
Using the Web address, the proxy tries to locate the requested object in its object store (cache).
3.
If the object is in the cache, the proxy checks to see if the object is fresh enough to serve (see Ensuring cached object freshness). If the object is fresh, the proxy serves it to the user as a cache hit.
4.
If the data in the cache is stale, the proxy connects to the origin server and asks if the object is still fresh (a revalidation). If the object is still fresh, the proxy sends the cached copy to the user immediately.
5.
If the object is not in the cache (a cache miss) or the server indicates that the cached copy is no longer valid, the proxy obtains the object from the origin server, simultaneously streaming it to the user and the cache. Subsequent requests for the object will be served faster because the object will come directly from the cache.
Print print article Email email article Font Size: A A

Search

Article Rating:

Do you have any additional feedback?    Email: close

Related Articles

Quick Links

Service Requests

How are we doing?

Provide us feedback on your experience with the Service Request portal.

provide feedback >

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Web Proxy Caching