请输入您要查询的百科知识:

 

词条 Web cache
释义

  1. Systems

      Forward position system (recipient or client side)    Reverse position system (content provider or web-server side)  

  2. Cache control

  3. Legal issues

  4. Web caching software

  5. See also

  6. References

  7. Further reading

  8. External links

A web cache (or HTTP cache) is an information technology for the temporary storage (caching) of Web documents, such as web pages, images, and other types of Web multimedia, to reduce server lag. A web cache system stores copies of documents passing through it; subsequent requests may be satisfied from the cache if certain conditions are met.[1] A web cache system can refer either to an appliance, or to a computer program.

Systems

Web caches can be used in various systems (as viewed from direction of delivery of web content):

Forward position system (recipient or client side)

A forward cache is a cache outside the web server's network, e.g. on the client computer, in an ISP or within a corporate network.[2] A network-aware forward cache is just like a forward cache but only caches heavily accessed items.[3] A client, such as a web browser, can also 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 whether to store web content.

Reverse position system (content provider or web-server side)

A reverse cache sits in front of one or more web servers and web applications, accelerating requests from the Internet, reducing peak web server load. A content delivery network (CDN) can retain copies of web content at various points throughout a network. A search engine may also cache a website; it provides a way of retrieving information from websites that have recently gone down or a way of retrieving data more quickly than by clicking the direct link. Google, for instance, does so. Links to cached contents may be found in Google search results.

Cache control

HTTP defines three basic mechanisms for controlling caches: freshness, validation, and invalidation.[4]
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.

Many CDNs and manufacturers of network equipment have replaced this standard HTTP cache control with dynamic caching.

{{See also | No-cache tag}}

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.

Web caching software

The following is a list of dedicated web caching server software:

NameOperating systemForward
mode
Reverse
mode
License
Apache HTTP Server Windows, OS X, Linux, Unix, FreeBSD, Solaris, Novell NetWare, OS/2, TPF, OpenVMS and eComStation{{No}}{{Yes}}Apache License 2.0}}
aiScaler Dynamic Cache Control Linux {{Yes}} {{Yes}} {{Proprietary}}
ApplianSys CACHEbox Linux {{Yes}} {{Yes}} {{Proprietary}}
Blue Coat ProxySG SGOS {{Yes}} {{Yes}} {{Proprietary}}
Nginx Linux, BSD variants, OS X, Solaris, AIX, HP-UX, other *nix flavors {{No}} {{Yes}}2-clause BSD-like}}
Microsoft Forefront Threat Management Gateway Windows {{Yes}} {{Yes}} {{Proprietary}}
Polipo Windows, OS X, Linux, OpenWrt, FreeBSD {{Yes}} {{Yes}}MIT License}}
Squid Linux, Unix, Windows {{Yes}} {{Yes}}GNU General Public License}}
Traffic Server Linux, Unix {{Yes}} {{Yes}}Apache License 2.0}}
Untangle Linux {{Yes}} {{Yes}} {{Proprietary}}
Varnish Linux, Unix {{Yes}} (possible with a VMOD) {{Yes}}BSD}}
WinGate Windows {{Yes}} {{Yes}} {{Proprietary}} / Free for 3 users
NusterLinux, Unix {{No}} {{Yes}}GNU General Public License}}

See also

  • Content delivery network (CDN)
  • Harvest project
  • Proxy server
  • Web accelerator
  • Cache manifest in HTML5

References

1. ^{{cite web | title=Web Caching | url=http://www.cisco.com/web/about/ac123/ac147/ac174/ac199/about_cisco_ipj_archive_article09186a00800c8903.html | publisher=Cisco. The Internet Protocol Journal - Volume 2, No. 3 | author=Geoff Huston | accessdate=2009-09-10}}
2. ^{{cite web |url=http://www.isaserver.org/tutorials/Understanding-Web-Caching-Concepts-ISA-Firewall.html |title=Understanding Web Caching Concepts for the ISA Firewall |first=Thomas |last=Shinder |access-date=27 February 2011 |date=2 September 2008 |work=ISA Server |archive-url=http://web.archive.org/web/20110723104247/http://www.isaserver.org/tutorials/Understanding-Web-Caching-Concepts-ISA-Firewall.html |archive-date=23 July 2011 |publisher=TechGenix Ltd.}}
3. ^{{cite paper |url=http://www.research.att.com/export/sites/att_labs/techdocs/TD_7LAUDD.pdf |citeseerx=10.1.1.159.1786 |title=Network-Aware Forward Caching |first=Jeffrey |last=Erman |first2=Alexandre |last2=Gerber |first3=Mohammad T. |last3=Hajiaghayi |first4=Dan |last4=Pei |first5=Oliver |last5=Spatscheck |work=AT&T Labs |year=2008 |access-date=11 March 2019 |archive-url=http://web.archive.org/web/20110401145549/http://www.research.att.com/export/sites/att_labs/techdocs/TD_7LAUDD.pdf |archive-date=1 April 2011 |pages=291-300}}
4. ^{{cite web |url=http://ws-rest.org/files/03-Link%20Header-based%20Invalidation%20of%20Caches.pdf |title=Using HTTP Link: Header for Gateway Cache Invalidation |format=PDF |access-date=14 June 2013 |first=Mike |last=Kelly |first2=Michael |last2=Hausenblas |pages=20 |work=WS-REST}}

Further reading

  • 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

  • [https://mid.as/kb/article/00149 How to clear your browser's web cache]
  • [https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching HTTP Caching]
  • Web Caching, Web caching in general with some references to SQUID
  • [https://www.maxcdn.com/one/visual-glossary/web-cache/ What is a Web Cache?]
{{DEFAULTSORT:Web Cache}}

3 : Hypertext Transfer Protocol|Cache (computing)|Proxy servers

随便看

 

开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。

 

Copyright © 2023 OENC.NET All Rights Reserved
京ICP备2021023879号 更新时间:2024/11/12 3:23:24