167736 - filetype is cached even if server changes content-type

Status: RESOLVED DUPLICATE of bug 198072

(Core :: Networking: Cache, defect)

Description

[Per Olofsson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826

If you click on a link that hands out a file of a certain filetype, say
application/octet-stream for an unknown file, then go into the server config and
update it so that it serves it with a different filetype, like text/plain,
mozilla has cached the filetype and won't listen.


Reproducible: Always

Steps to Reproduce:
1. click on foo.bar on myserver.com
2. cancel the file dialog that pops up for application/octet-stream
3. update myserver.com to server .bar files as text/plain
4. click on foo.bar on myserver.com again

Actual Results:  
file dialog asking me to save an application/octet-stream file

Expected Results:  
display the file as text/plain.


Clearing the cache helps of course.

Comment 1

[Boris Zbarsky [:bzbarsky]]

What's your cache setting?  (compare once, every time, never?)  Your server
probably sends the same last-modified date for the file the second time and does
not specify a Vary: header, hence the change in content-type does not trigger
cache invalidation....

Comment 2

[Per Olofsson]

The cache is set to compare when the page is out of date. And yes, the only
thing that the server changes in the header is the content-type, but IMHO this
should be enough to trigger a cache invalidation.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Why?  The page is not out of date....  If the server sends a different
X-Message-Of-The-Hour header, should that invalidate the cache too?

Comment 4

[gordon]

If the page hasn't expired, we don't even bother asking the server if there have
been any changes, so there's no way for us to know that it's changed the doc type.

Marking INVALID.

Comment 5

[benc]

REOPEN:
please check your server logs.
If you sent back something like a 304 to th second request, your updated didn't
take effect on the server.

Comment 6

[benc]

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

Comment 7

[Harveer Singh]

Attachment: Bug 167736: Introducing a new about page 'about:storage'. r=#dom-storage-reviewers,janv,jstutte

Comment 8

[Phabricator Automation]

Comment on attachment 9278813 [details]
Bug 167736: Introducing a new about page 'about:storage'. r=#dom-storage-reviewers,janv,jstutte

Revision D147686 was moved to bug 1677736. Setting attachment 9278813 [details] to obsolete.