From 1fea24fd5c0d603fef5a63331711603400435172 Mon Sep 17 00:00:00 2001 From: Ray Schamp Date: Fri, 14 Oct 2016 14:24:28 -0400 Subject: [PATCH] Use no-cache so ETags are used From https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching > "no-cache" indicates that the returned response can't be used to satisfy a subsequent request to the same URL without first checking with the server if the response has changed. As a result, if a proper validation token (ETag) is present, no-cache incurs a roundtrip to validate the cached response, but can eliminate the download if the resource has not changed. This is what we want to happen. --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index bc291cc32..e94100fb3 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ ESLINT=./node_modules/.bin/eslint NODE=node SASSLINT=./node_modules/.bin/sass-lint -v -S3CMD=s3cmd sync -P --delete-removed --add-header=Cache-Control:public,max-age=3600 +S3CMD=s3cmd sync -P --delete-removed --add-header=Cache-Control:no-cache,public,max-age=3600 TAP=./node_modules/.bin/tap WATCH=./node_modules/.bin/watch WEBPACK=./node_modules/.bin/webpack