From dc44141dd06adc56d563da649eb4d5a9d18dcc31 Mon Sep 17 00:00:00 2001 From: uvok cheetah Date: Sun, 17 May 2020 18:07:33 +0200 Subject: Add thoughts about caching --- .../2020-05-17-why-is-browser-caching-so-weird.md | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 _posts/2020-05-17-why-is-browser-caching-so-weird.md (limited to '_posts') diff --git a/_posts/2020-05-17-why-is-browser-caching-so-weird.md b/_posts/2020-05-17-why-is-browser-caching-so-weird.md new file mode 100644 index 0000000..adfc542 --- /dev/null +++ b/_posts/2020-05-17-why-is-browser-caching-so-weird.md @@ -0,0 +1,25 @@ +--- +layout: post +title: Why is browser caching so weird? +date: 2020-05-17 18:02 +0200 +tags: jekyll, webdev +categories: tech +--- + +I wondered for a while about this... Every time I added an entry to my blog, regenerated +and reuploaded it... When I typed `blog.uvokchee.de` in my browser, it would open the old +index.html. I had to manually refresh (Ctrl-R / F5, not even Ctrl-Shift-R to circumvent +the cache) the page so it displayed the new entry. This confuses me utterly. + +Up until now, no headers were sent by the server except `ETags`. So... what is the default +browser caching behavior? I'm glad about any input about that. + +For now, I added this to `.htaccess`, lets see if this helps. \*shrugs\* + +``` + +ExpiresActive on +ExpiresDefault "access plus 1 week" +ExpiresByType text/html "access plus 0 seconds" + +``` -- cgit v1.2.3