487020 - seems certain pages are cached and do not refresh until restarting the browser.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Marc Plotz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)

I develop websites. Recently I was updating pages on a site and noticed they were not changing once saved. investigations on various machines using firefox 3.08 showed that the pages were being cached. Tested different sites on different servers, had the same problem. Edit a file on a site and refresh (ctrl+f5) does not update the changes from the browser but seems to render a cached version of what was there before you changed it.

Reproducible: Always

Steps to Reproduce:
1. view website page
2. edit something on that file
3. refresh page. it hasnt changed (ctrl+f5)
Actual Results:  
The pages did not refresh

Expected Results:  
the page should have changed

tried this with multiple firefoc 3.08 browsers on different machines, one even in a different part of the country, same error although different sites, as well as localhost were used

Comment 1

[Skaman Sam Tyler]

IMO, this is a _serious_ problem!

I have encountered this issue with 3.0.10 and 3.5b4 (the latest stable and beta releases). 

Here's what all I have tried to get the pages to display properly:
   - disabling all extensions and add-ons
   - disabling the cache with the Developer ToolBar
   - closing all tabs, restarting, clearing the cache, and restarting again. 
   - viewing the CSS by typing in the URL of the stylesheet. This displays the 
     changes, but after viewing the html file again, does not apply them to 
     the page!

The only way to get the new page to display properly  is edit the CSS page in Firebug. Simply adding a space to the file in Firebug will cause it to render properly.

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Try shift-refresh to force a flush of all the caches? There's a bunch of caching issues that can come into play, here.

Clearing all blocking nomination flags until we get a narrowed description of the problem or set of steps to reproduce.

Comment 3

[Shawn Wilsher :sdwilsh]

Likely bug 183470, but no response from the reporter, so INCOMPLETE.