129515 - browser caches mimetype info? if server changes mimetype browser not aware

Status: RESOLVED DUPLICATE of bug 198072

(Core :: Networking: Cache, defect)

Description

[Peter Yellman]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020406

Browser does not take note of changes in mimetype as provided by server.  For
example, default apache/Red Hat install does not map xls extension to msexcel
mimetype (vnd.ms-excel, to be specific).  After mapping that extension to xls in
server mime.types and restarting server, Mozilla not aware of new mimetype info.

Resolution: manually delete ALL cache files from Mozilla cache directory.

Using cache clearing from within Mozilla, and/or restarting does not resolve.






Reproducible: Always
Steps to Reproduce:
1. attempt to download file of selected type, note mimetype
2. change mimetype at server, restart
3. attempt download of file, note mimetype

Actual Results:  Mozilla continues to see the file as mimetype from the first
download attempt.

Expected Results:  Mozilla will re-read mimetype info being provided by server
and act accordingly.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Mozilla caches the entire server response (headers, data, etc).  This is in fact
the only reasonable thing to cache.  When we then get the file again, we just
read it from our cache, headers and all.  This is necessary for proper
functioning of the cache in general....

Comment 2

[Jimmy Lee]

Catching up.  Please reopen bug if there is still a problem.  Marking Verified!

Comment 3

[benc]

REOPEN:

I'd like gordon+tom to look at this before closing. There might be some user
concerns they should hear, plus, we don't know if their cache settings are
correct. Since this is also a downloaded file, it seems to me it should not live
in cache;

Comment 4

[benc]

-> cache, -> new, based on bz's comments.

Comment 5

[gordon]

I think this is the same issue as bug 198072.  Shift-Reload should load the
updated document without have to clear the entire cache.



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