30670 - "clear memory cache" preferences button has no effect

Status: VERIFIED WORKSFORME

(Core :: Networking: Cache, defect, P3)

Description

[David A. Madore]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.13-lazuli i686; en-US; m14)
BuildID:    2000030312

Clicking on the "Clear Memory Cache" button in the
Edit/Preferences/Advanced/Cache section does not seem to have any effect.
Netscape still sends If-None-Mach or If-Modified-Since headers and accepts a 304
Not Modified reply without complaining.

Reproducible: Always
Steps to Reproduce:
1. Disactivate disk cache but leave memory cache.
2. Load any page.
3. Click on "Clear Memory Cache".
4. Reload document.


Actual Results:  The HTTP request sent is exactly identical to that obtained if
the memory cache is not cleared.	

Expected Results:  No If-Modified-Since and If-None-Match headers should be
sent.  In fact, Mozilla should not be *able* to send such headers.

In combination to bug 30663 this does not solve the problem described there.

I do not know whether the problem is due to the actual cache component, or to
the preferences button.

Comment 1

[rods (gone)]

*** This bug has been marked as a duplicate of 18579 ***

Comment 2

[David A. Madore]

Uh?  I can't see any relation with bug 18579.  I expected this bug to be a
duplicate, but I couldn't find any matching entry anywhere.  Surely 18579 is not
what you mean.

Maybe this is a bug in the Bugzilla search engine, though: see bug 30672 and see
if it seems to correspond.

Comment 3

[fig\tree]

this bug definitely isn't a dupe of bug 18579, reopening.

Comment 4

[Asa Dotzler [:asa]]

setting status to new.  

Comment 5

[Gagan]

Here is Neeti's quote--
   The debug preferences panel for mem cache is broken. 
    The pref string in  
/xpfe/components/prefwindow/resources/content/pref-debug.xul 
     is specified as browser.enable.cache, 

 <checkbox id="browserEnableCache" value="&debugEnableMemCache.label;" 
110               pref="true" preftype="bool" prefstring="browser.enable.cache" 
111               prefattribute="checked"/> 

whereas the actual pref string defined in all.js for mem cache is 

browser.cache.enable 
pref("browser.cache.enable",                true); 

Since this is set to true, mem cache is enabled. 

Comment 6

[Gagan]

*** Bug 47056 has been marked as a duplicate of this bug. ***

Comment 7

[fig\tree]

bug 47056 is actually a dupe of bug 44766. This bug and 44766 are related but
not the same thing. Thus I think 44766 should remain related but not duped to
this bug.

Comment 8

[neeti]

*** Bug 44766 has been marked as a duplicate of this bug. ***

Comment 9

[neeti]

I just tried this, and I am not able to reproduce the problem

1. Disactivate disk cache but leave memory cache.
2. Load tinderbox page.
3. Click on "Clear Memory Cache". This is actually deleting all memory records ( 
verified in debugger)
4. Reload tinderbox document.( Mozilla is not sending If-Modified-Since and 
If-None-Match headers, verified in debugger).

I am marking this bug WORKSFORME, and reopening 47056 and 44766.

Neeti

Comment 10

[neeti]

I just tried this, and I am not able to reproduce the problem

1. Disactivate disk cache but leave memory cache.
2. Load tinderbox page.
3. Click on "Clear Memory Cache". This is actually deleting all memory records ( 
verified in debugger)
4. Reload tinderbox document.( Mozilla is not sending If-Modified-Since and 
If-None-Match headers, verified in debugger).

I am marking this bug WORKSFORME, and reopening 47056 and 44766.

Neeti

Comment 11

[Tom Everingham]

verified wfm