From 29d33d3e52df53fd1080f2f8d1b2ea4cbbb420b5 Mon Sep 17 00:00:00 2001 From: "dp%netscape.com" Date: Thu, 7 Sep 2000 18:24:28 +0000 Subject: [PATCH] bug 48292 Releasing cache entry as soon as we are done rather than waiting until nsHTTPChannel gets deleted, which apparently happens after the next page finishes loading giving rise to all kinds of interesting conditions if the current and next page are same. r=neeti git-svn-id: svn://10.0.0.236/trunk@78398 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp b/mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp index 07fc421032e..0050ddb951d 100644 --- a/mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp +++ b/mozilla/netwerk/protocol/http/src/nsHTTPChannel.cpp @@ -1823,6 +1823,10 @@ nsresult nsHTTPChannel::ResponseCompleted(nsIStreamListener *aListener, } } + // Release the cache entry as soon as we are done. This helps as it can + // flush any cache records and do maintenance. + mCacheEntry = nsnull; + // // After the consumer has been notified, remove the channel from its // load group... This will trigger an OnStopRequest from the load group.