Revision as of 03:04, 25 October 2022 edit 2.147.115.52 (talk) No edit summary Tags: Reverted Mobile edit Mobile web edit ← Previous edit		Revision as of 03:14, 25 October 2022 edit undo Felida97 (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers 56,028 edits m Reverted edits by 2.147.115.52 (talk) (HG) (3.4.9) Tag: Rollback Next edit →
Line 2: A '''Web cache''' (or '''HTTP cache''') is a system for optimizing the [[World Wide Web]]. It is implemented both [[client-side]] and [[server-side]]. The [[cache (computing)\|caching]] of [[multimedia]]s and other [[computer file\|files]] can result in less overall delay when [[web browser\|browsing]] the Web.<ref>{{Cite web \|last=Fountis \|first=Yorgos \|date=4 May 2017 \|title=How does the browser cache work? \|url=https://pressidium.com/blog/2017/browser-cache-work/}}</ref> ~~Ylep legoog~~ ==Parts of the system== Line 12 ⟶ 11: ===HTTP options=== The [[Hypertext Transfer Protocol]] (HTTP) defines three basic mechanisms for controlling caches: freshness, validation, and invalidation.<ref>{{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 \|access-date=14 June 2013 \|first1=Mike \|last1=Kelly \|first2=Michael \|last2=Hausenblas \|pages=20 \|work=WS-REST}}</ref> This is specified in the header of HTTP response messages from the server. ~~[[YATAGARDBO]]~~ 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.

Web cache: Difference between revisions