You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by yo...@apache.org on 2022/12/13 06:52:38 UTC
[apisix-website] branch master updated: docs: update EN web-resource-caching blogs image (#1446)

This is an automated email from the ASF dual-hosted git repository.

young pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git


The following commit(s) were added to refs/heads/master by this push:
     new ca46d989fd5 docs: update EN web-resource-caching blogs image (#1446)
ca46d989fd5 is described below

commit ca46d989fd5b5850fcdc6c4c5e7ad48c4a8cc7a3
Author: Sylvia <39...@users.noreply.github.com>
AuthorDate: Tue Dec 13 14:52:32 2022 +0800

    docs: update EN web-resource-caching blogs image (#1446)
---
 blog/en/blog/2022/12/07/web-caching-client.md | 2 +-
 blog/en/blog/2022/12/14/web-caching-server.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/blog/en/blog/2022/12/07/web-caching-client.md b/blog/en/blog/2022/12/07/web-caching-client.md
index 5e68ec440ac..3e2ef34cf57 100644
--- a/blog/en/blog/2022/12/07/web-caching-client.md
+++ b/blog/en/blog/2022/12/07/web-caching-client.md
@@ -12,7 +12,7 @@ keywords:
   - Performance
 description: "The subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource caching can happen in two different places: client-side - on the browser and server-side. This post is dedicated to the former; the next post will focus on the latter."
 tags: [Case Studies]
-image: https://blog.frankel.ch/assets/resources/web-caching/pexels-tom-fisk-3063470.jpg
+image: https://static.apiseven.com/2022/12/13/63981dcbe4b0c.jpg
 ---
 
 >The subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource caching can happen in two different places: client-side - on the browser and server-side. This post is dedicated to the former; the next post will focus on the latter.
diff --git a/blog/en/blog/2022/12/14/web-caching-server.md b/blog/en/blog/2022/12/14/web-caching-server.md
index ea246a4523f..e675ace2071 100644
--- a/blog/en/blog/2022/12/14/web-caching-server.md
+++ b/blog/en/blog/2022/12/14/web-caching-server.md
@@ -12,7 +12,7 @@ keywords:
   - Performance
 description: "The subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource caching can happen in two different places: client-side - on the browser and server side. In the previous post, I explained the former; this post focuses on the latter."
 tags: [Case Studies]
-image: https://blog.frankel.ch/assets/resources/web-caching/pexels-tom-fisk-3063470.jpg
+image: https://static.apiseven.com/2022/12/13/63981be362ec4.jpg
 ---
 
 >The subject of Web resource caching is as old as the World Wide Web itself. However, I'd like to offer an as-exhaustive-as-possible catalog of how one can improve performance by caching. Web resource caching can happen in two different places: client-side - on the browser and server side. In the [previous post](https://blog.frankel.ch/web-caching/client/), I explained the former; this post focuses on the latter.