From 2d487972940e7fba1b791ff5b83b0aefd13a3e24 Mon Sep 17 00:00:00 2001 From: James Salter Date: Fri, 10 Sep 2021 11:18:06 +0100 Subject: [PATCH 1/2] Suggest setting Cache-Control: no-cache on / for self-hosters --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 4fd89c018a..1f1d31f7b9 100644 --- a/README.md +++ b/README.md @@ -238,6 +238,10 @@ Element requires the following URLs not to be cached, when/if you are serving El /index.html ``` +We also recommend that you force browsers to re-validate any cached copy of Element on page load by configuring your +webserver to return `Cache-Control: no-cache` for `/`. This ensures the browser will fetch a new version of Element on +the next page load after it's been deployed. + Development =========== From 5741baed2547038e3b66eb13023e27ce811462f5 Mon Sep 17 00:00:00 2001 From: James Salter Date: Wed, 29 Sep 2021 13:14:03 +0100 Subject: [PATCH 2/2] Note that caching is configured in he Dockerfile --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1f1d31f7b9..441ce5109b 100644 --- a/README.md +++ b/README.md @@ -240,7 +240,8 @@ Element requires the following URLs not to be cached, when/if you are serving El We also recommend that you force browsers to re-validate any cached copy of Element on page load by configuring your webserver to return `Cache-Control: no-cache` for `/`. This ensures the browser will fetch a new version of Element on -the next page load after it's been deployed. +the next page load after it's been deployed. Note that this is already configured for you in the nginx config of our +Dockerfile. Development ===========