If neighbors don't support our private keys, then we can't use the

httpMaybeRemovePublic() function because ALL entries are public and
we end up removing our own.

diff --git a/src/http.cc b/src/http.cc
index eeeb74f8089690bcb3d16c08c418744fa71a74dc..720574c0fd2885e9935332abeeedd5ce039c97b7 100644 (file)
--- a/src/http.cc
+++ b/src/http.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: http.cc,v 1.314 1998/09/04 23:04:50 wessels Exp $
+ * $Id: http.cc,v 1.315 1998/09/10 19:45:53 wessels Exp $
  *
  * DEBUG: section 11    Hypertext Transfer Protocol (HTTP)
  * AUTHOR: Harvest Derived
@@ -298,7 +298,8 @@ httpProcessReplyHeader(HttpStateData * httpState, const char *buf, int size)
        storeTimestampsSet(entry);
        /* Check if object is cacheable or not based on reply code */
        debug(11, 3) ("httpProcessReplyHeader: HTTP CODE: %d\n", reply->sline.status);
-       httpMaybeRemovePublic(entry, reply->sline.status);
+       if (neighbors_do_private_keys)
+           httpMaybeRemovePublic(entry, reply->sline.status);
        switch (httpCachableReply(httpState)) {
        case 1:
            httpMakePublic(entry);