Web Cache Article Index for
Web 		Website Links For
Web 		 

Information About

Web Cache
  CATEGORIES ABOUT WEB CACHE
   
servers
   
http
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...




TYPES OF WEB CACHES

Web caches can be deployed in a variety of ways. User Agent caches, such as those in Web Browser s, are ''private caches'', operating on behalf of a single user. Intermediaries can also implement ''shared caches'' that serve more than one person.

Proxy caches, also known as ''forward proxy caches'', are usually deployed by Internet Service Provider s, schools and corporations to save bandwidth. Interception proxy caches (sometimes called "transparent caches") are a variant that doesn't require clients to be explicitly configured to use them.

Gateway caches, sometimes known as Reverse Proxy caches, ''surrogate caches'', or Web Accelerator s, operate on behalf of the origin server, and to clients are indistinguisable from it. A number of Gateway caches can work together to implement a Content Delivery Network .

Intermediaries that cache often perform other duties, such as user Authentication and Content Filtering . Multiple caches can also be coordinated using ''peering protocols'' like Internet Cache Protocol and HTCP .


CONTROLLING WEB CACHES

HTTP defines three basic mechanisms for controlling caches: freshness, validation and invalidation.

  • Freshness allows a response to be used without re-checking it on the origin server, and can be controlled by both the server and the client. For example, the Expires response header gives a date when the document becomes stale, and the Cache-Control: max-age directive tells the cache how many seconds the response is fresh for.

  • Validation can be used to check whether a cached response is still good after it becomes stale. For example, if the response has a Last-Modified header, a cache can make a ''conditional request'' using the If-Modified-Since header to see if it has changed.

  • Invalidation is usually a side effect of another request that passes through the cache. For example, if URL associated with a cached response subsequently gets a POST, PUT or DELETE request, the cached response will be invalidated.


In 1998 the DMCA added rules to the United States Code ( 17 U.S.C. ยง 512 ) that largely relieves system operators from copyright liability for the purposes of caching.


SEE ALSO



REFERENCES

  • Ari Luotonen, ''Web Proxy Servers'' (Prentice Hall, 1997) ISBN 0-13-680612-0

  • Duane Wessels, ''Web Caching'' (O'Reilly and Associates, 2001). ISBN 1-56592-536-X

  • Michael Rabinovich and Oliver Spatschak, ''Web Caching and Replication'' (Addison Wesley, 2001). ISBN 0-201-61570-3



EXTERNAL LINKS