654357 - Cache sticking - no modification check so that newly added/edited page content would be displayed after initial page visit

Status: RESOLVED DUPLICATE of bug 579846

(Core :: DOM: HTML Parser, defect)

Description

[E B]

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

1. You open web page

2. I edit index.htm of the web page which includes code forcing web browsers to do a modification check and display newly added/edited content since your last visit.
 
<meta http-equiv="Last-Modified" content="02 May, 2011  at 07:54:24" />
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="pragma" content="no-cache">

3. You open same web page again but do not see edits without Reloading the page.

Internet Explorer and Google Chrome display modified web page but Firefox 4.0.1 requires a page Reload to display newly added content.


Reproducible: Always

Steps to Reproduce:
1. You open web page
2. I edit index.htm
3. You open same web page again and instead of seeing edits without Reloading the page, you can only see them if you refresh the page.

Actual Results:  
1. You open web page
2. I edit index.htm
3. You open same web page again and instead of seeing edits without Reloading the page, you can only see them if you refresh the page.

Expected Results:  
1. You open web page
2. I edit index.htm
3. You open same web page again and just like if using IE or Google Chrome, you would see added/edited content without needing to Reload page.

Reproduced without add-ons or modifications to Firefox 4.0.1.

Comment 1

[Thomas Ahlblom]

I'm not sure it's relevant for the alleged bug, but what standard do you use for date and time in Last-Modified? It doesn't look like RFC 822  / RFC 1123.

What does the output on your Web Console look like when reproducing? Do you get any "HTTP/1.1 304 Not Modified" entries?

Comment 2

[Boris Zbarsky [:bzbarsky]]

Henri, you removed support for all that stuff in http-equiv, right?

Comment 3

[Henri Sivonen (:hsivonen)]

(In reply to comment #2)
> Henri, you removed support for all that stuff in http-equiv, right?

Yes. Sites need to use real HTTP headers to control caching now.