Bug #876: Incomplete objects may appear stuck in the cache

Under certain conditions incomplete objects may appear stuck in the cache,
not even reload giving a new fresh copy.

diff --git a/src/client_side_reply.cc b/src/client_side_reply.cc
index a8cb02ca428dbaaa132a7a8e4f1de0bcfc3f8fe1..4a024bdcb9d9dcc2514103ca6046cffa7be819e2 100644 (file)
--- a/src/client_side_reply.cc
+++ b/src/client_side_reply.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: client_side_reply.cc,v 1.68 2004/04/03 14:25:59 hno Exp $
+ * $Id: client_side_reply.cc,v 1.69 2004/04/04 13:52:42 hno Exp $
  *
  * DEBUG: section 88    Client-side Reply Routines
  * AUTHOR: Robert Collins (Originally Duane Wessels in client_side.c)
@@ -1547,17 +1547,6 @@ clientReplyContext::identifyFoundObject(StoreEntry *newEntry)
         return;
     }
 
-#if HTTP_VIOLATIONS
-    if (http->storeEntry()->store_status == STORE_PENDING) {
-        if (r->flags.nocache || r->flags.nocache_hack) {
-            debug(85, 3) ("Clearing no-cache for STORE_PENDING request\n\t%s\n",
-                          storeUrl(http->storeEntry()));
-            r->flags.nocache = 0;
-            r->flags.nocache_hack = 0;
-        }
-    }
-
-#endif
     if (r->flags.nocache) {
         debug(85, 3) ("clientProcessRequest2: no-cache REFRESH MISS\n");
         http->storeEntry(NULL);