Cache-Control header has no influence on IMS headers




Networking: HTTP
14 years ago
12 years ago


(Reporter: Sander Rijken, Assigned: Darin Fisher)


Windows XP

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040119
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040119

Mozilla keeps sending IMS headers, no matter what the Cache-Control is set to.
This is a cause for problems when used with the IIS-Tomcat combination. Mozilla
askes if the page is modified, IIS-Tomcat says: 304, not modified.
Then sometimes nothing happens, and sometimes the 304 error shows.
The 304 is always sent according to the Live HTTP headers plugin, and it should
be sent, cause Mozilla is asking if page is modified.

Reproducible: Always

Steps to Reproduce:
1.Setup IIS and Tomcat with J2K plugin
2.Create a HTML page on IIS and one on Tomcat
3.All the pages have a Cache-Control: no-cache header
4.Link the IIS one to the Tomcat one

Actual Results:  
First time (or after clearing cache), page opens in Tomcat.
Next times nothing happens, or 304 shows

Expected Results:  
Mozilla should not send a If-Modified-Since header, since Cache-Control is set
to no-cache

Comment 1

14 years ago
There is a workaround for this problem.
in about:config setting browser.cache.enabled to false provides a workaround.

Comment 2

14 years ago
Alternatively, another workaround would be to have the server surpress the Last-
Modified header. Without it, we won't send If-Modified-Since (IIRC). This still 
sounds like a bug, though.

Comment 3

14 years ago
Forgive me for a stupid question, but if IIS/Tomcat is sending "Cache-Control:
no-cache", why is it answering with a 304 on a If-Modified-Since ? That might be
true, but what does the poor browser have to do then ? The server doesn't want
to sent it, and the cache doesn't have a copy. Ofcourse, the fact is Mozilla is
sending the IMS is an error, but IIS/Tomcat's response is just as worse. 
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.