Browser cache

"Bypass your cache" redirects here. For instructions on bypassing your cache on World Heritage Encyclopedia, see World Heritage Encyclopedia:Bypass your cache.
For a site that keeps old versions of web pages, see web archive.

A web cache is a mentorism for the temporary storage (caching) of web documents, such as HTML pages and images, to reduce bandwidth usage, server load, and perceived lag. A web cache stores copies of documents passing through it; subsequent requests may be satisfied from the cache if certain conditions are met.[1] Google's cache link in its search results provides a way of retrieving information from websites that have recently gone down and a way of retrieving data more quickly than by clicking the direct link.

Systems

Web caches can be used in various systems.

  • A search engine may cache a website.
  • A forward cache is a cache outside the webserver's network, e.g. on the client software's ISP or company network.[2]
  • A network-aware forward cache is just like a forward cache but only caches heavily accessed items.[3]
  • A reverse cache sits in front of one or more Web servers and web applications, accelerating requests from the Internet.[4]
  • A client, such as a web browser, can store web content for reuse. For example, if the back button is pressed, the local cached version of a page may be displayed instead of a new request being sent to the web server.
  • A web proxy sitting between the client and the server can evaluate HTTP headers and choose to store web content.
  • A content delivery network can retain copies of web content at various points throughout a network.

Cache control

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

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. The ETag (entity tag) mechanism also allows for both strong and weak validation.
Invalidation 
is usually a side effect of another request that passes through the cache. For example, if a URL associated with a cached response subsequently gets a POST, PUT or DELETE request, the cached response will be invalidated.

Legal issues

In 1998, the DMCA added rules to the United States Code (17 U.S.C. §: 512) that relinquishes system operators from copyright liability for the purposes of caching.

Comparison of web caches

Name Type Operating System Forward
Mode
Reverse
Mode
License
Apache HTTP Server Software Linux, Unix, Windows, ... Yes Yes Apache License 2.0
ApplianSys CACHEbox Appliance Linux Yes Yes Proprietary
Blue Coat ProxySG Appliance SGOS Yes Yes Proprietary
Nginx Software Linux, Unix Yes Yes 2-clause BSD-like
Microsoft Forefront Threat Management Gateway Software Windows Yes Yes Proprietary
Polipo Software Linux, Unix, Windows Yes Yes MIT License
Squid Software Linux, Unix, Windows Yes Yes GNU GPL
Traffic Server Software Linux, Unix Yes Yes Apache License 2.0
Untangle Software Linux Yes Yes Proprietary
Varnish Software Linux, Unix Yes Yes BSD
WinGate Software Windows Yes Yes Proprietary / Free for 3 users

Notes

Further reading

External links

  • Caching Tutorial for Web Authors and Webmasters
  • Web Caching and Content Delivery Resources
  • Web Caching, Web caching in general with some references to SQUID
  • Cache control directives demystified Explanations, do's and don't
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.