net/haproxy/patches/0037-MINOR-http-status-301-should-not-be-marked-non-cache.patch

   1 From 6c9ba3562cf57dc033a52c0973962c642b3aaf18 Mon Sep 17 00:00:00 2001
   2 From: Yves Lafon <ylafon@w3.org>
   3 Date: Mon, 11 Mar 2013 11:06:05 -0400
   4 Subject: [PATCH 37/42] MINOR: http: status 301 should not be marked
   5  non-cacheable
   6
   7 Also, browsers behaviour is inconsistent regarding the Cache-Control
   8 header field on a 301.
   9 (cherry picked from commit e267421e93eb35272a104c9c8fa6878880f42be8)
  10 ---
  11  src/proto_http.c | 1 -
  12  1 file changed, 1 deletion(-)
  13
  14 diff --git a/src/proto_http.c b/src/proto_http.c
  15 index 8d9d8e8..a52c038 100644
  16 --- a/src/proto_http.c
  17 +++ b/src/proto_http.c
  18 @@ -73,7 +73,6 @@ const struct chunk http_100_chunk = {
  19  /* Warning: no "connection" header is provided with the 3xx messages below */
  20  const char *HTTP_301 =
  21         "HTTP/1.1 301 Moved Permanently\r\n"
  22 -       "Cache-Control: no-cache\r\n"
  23         "Content-length: 0\r\n"
  24         "Location: "; /* not terminated since it will be concatenated with the URL */
  25
  26 --
  27 1.8.1.5
  28