From 0914f5b0634e250fbc98e2062488474cb81226ec Mon Sep 17 00:00:00 2001 From: Jxck Date: Tue, 14 Jan 2025 18:47:03 +0900 Subject: [PATCH 1/2] replace images w/ shared-assets --- files/en-us/web/http/caching/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/files/en-us/web/http/caching/index.md b/files/en-us/web/http/caching/index.md index e1e15b122d31759..552ce31a2ae66b7 100644 --- a/files/en-us/web/http/caching/index.md +++ b/files/en-us/web/http/caching/index.md @@ -72,7 +72,7 @@ That means if a managed cache intentionally ignores a `no-store` directive, ther Note that some CDNs provide their own headers that are effective only for that CDN (for example, `Surrogate-Control`). Currently, work is underway to define a [`CDN-Cache-Control`](https://httpwg.org/specs/rfc9213.html) header to standardize those. -![Type of Cache](type-of-cache.png) +![Type of Cache](https://mdn.github.io/shared-assets/images/diagrams/http/cache/type-of-cache.svg) ## Heuristic caching @@ -481,7 +481,7 @@ Request collapse occurs when requests are arriving at the same time, so even if If the response is personalized to a particular user and you do not want it to be shared in collapse, you should add the `private` directive: -![Request Collapse](request-collapse.png) +![Request Collapse](https://mdn.github.io/shared-assets/images/diagrams/http/cache/request-collapse.svg) ## Common caching patterns From ca00753afc8549887144970d593483f9fe46c89a Mon Sep 17 00:00:00 2001 From: Brian Smith Date: Fri, 24 Jan 2025 11:34:43 +0100 Subject: [PATCH 2/2] Add some alt text to diagrams --- files/en-us/web/http/caching/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/files/en-us/web/http/caching/index.md b/files/en-us/web/http/caching/index.md index 552ce31a2ae66b7..650c03848827e4d 100644 --- a/files/en-us/web/http/caching/index.md +++ b/files/en-us/web/http/caching/index.md @@ -72,7 +72,7 @@ That means if a managed cache intentionally ignores a `no-store` directive, ther Note that some CDNs provide their own headers that are effective only for that CDN (for example, `Surrogate-Control`). Currently, work is underway to define a [`CDN-Cache-Control`](https://httpwg.org/specs/rfc9213.html) header to standardize those. -![Type of Cache](https://mdn.github.io/shared-assets/images/diagrams/http/cache/type-of-cache.svg) +![Types of caches, including a private cache in the browser, a shared (proxy) cache, a reverse proxy cache, and a shared (managed) cache in a CDN, leading to the origin server's cache](https://mdn.github.io/shared-assets/images/diagrams/http/cache/type-of-cache.svg) ## Heuristic caching @@ -481,7 +481,7 @@ Request collapse occurs when requests are arriving at the same time, so even if If the response is personalized to a particular user and you do not want it to be shared in collapse, you should add the `private` directive: -![Request Collapse](https://mdn.github.io/shared-assets/images/diagrams/http/cache/request-collapse.svg) +![Request collapse shown as multiple clients sending GET requests and a cache consolidating them into one GET to the origin. The origin server responds with a 200 OK that the cache shares back to all clients.](https://mdn.github.io/shared-assets/images/diagrams/http/cache/request-collapse.svg) ## Common caching patterns