From 5613c60dd88ebcdda984be3f02fe4ed8fe8825ef Mon Sep 17 00:00:00 2001
From: Garri Djavadyan <garryd@comnet.uz>
Date: Tue, 15 Nov 2016 02:17:06 +1300
Subject: [PATCH] Bug 3533: Cache still valid after HTTP/1.1 303 See Other

RFC7231 does not mention 303 response as non-cacheable.
So, assuming that means it *is* cacheable.
---
 src/http.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/http.cc b/src/http.cc
index 734dbcac54..ca61909e12 100644
--- a/src/http.cc
+++ b/src/http.cc
@@ -202,6 +202,8 @@ httpMaybeRemovePublic(StoreEntry * e, Http::StatusCode status)
 
     case Http::scFound:
 
+    case Http::scSeeOther:
+
     case Http::scGone:
 
     case Http::scNotFound:
-- 
2.39.2