From 7a1b008054760579dd67cd410f7510d2e1f250c6 Mon Sep 17 00:00:00 2001
From: Tatuya Kamada <tatuya@nexedi.com>
Date: Tue, 8 May 2012 18:03:57 +0900
Subject: [PATCH] Stop removing Expires header reason: - Expires header is
widely supported than max-age. e.g.: HTTP/1.0 clients. - max-age directive
always overrides Expires setting under HTTP/1.1, so there is no need to
remove Expires here.
---
slapos/recipe/generic_varnish/template/default.vcl.in | 2 --
1 file changed, 2 deletions(-)
diff --git a/slapos/recipe/generic_varnish/template/default.vcl.in b/slapos/recipe/generic_varnish/template/default.vcl.in
index 220bc446c..e26b67fe6 100644
--- a/slapos/recipe/generic_varnish/template/default.vcl.in
+++ b/slapos/recipe/generic_varnish/template/default.vcl.in
@@ -157,8 +157,6 @@ sub vcl_fetch {
if (beresp.ttl > 0s) {
/* Setup grace period for 30days for all cacheable contents */
set beresp.grace = 30d;
- /* Remove Expires from backend, it's not long enough */
- unset beresp.http.expires;
# /* Set the clients TTL on this object */
# set beresp.http.cache-control = "max-age = 300";
/* Set how long Varnish will keep it */
--
2.30.9