Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Development: Ctrl+Shift+R don't clean the cash (only manually or through plugin)

  • 7 antwurd
  • 4 hawwe dit probleem
  • 2 werjeftes
  • Lêste antwurd fan Xixo

more options

I am developing a web application (Wildfly, JS, html, css & co.). I am checking that in both Chrome and Firefox, but in Firefox every time i want to refresh a page to see changes, i must clean the cache, while in Chrome i just press F5. I installed Firefox Developer Edition because of that, but the problem is also there.

Even Ctrl+Shift+R doesn't solve the problem (or not always).

I added: https://addons.mozilla.org/it/firefox/addon/empty-cache-button/ and it works great. But still, why doesn't work just F5 as it happens in Chrome? Is there an option "automatically clean cache"? Or some "Developement mode" that allows to refresh everything silently?

The biggest disappointment was when i saw that this happens also in "Firefox Developer Edition" Maybe i am doing something wrong or the option is present?

I remember some problems like that in the past, but now they happens almost on always change.

I am developing a web application (Wildfly, JS, html, css & co.). I am checking that in both Chrome and Firefox, but in Firefox every time i want to refresh a page to see changes, i must clean the cache, while in Chrome i just press F5. I installed Firefox Developer Edition because of that, but the problem is also there. Even Ctrl+Shift+R doesn't solve the problem (or not always). I added: https://addons.mozilla.org/it/firefox/addon/empty-cache-button/ and it works great. But still, why doesn't work just F5 as it happens in Chrome? Is there an option "automatically clean cache"? Or some "Developement mode" that allows to refresh everything silently? The biggest disappointment was when i saw that this happens also in "Firefox Developer Edition" Maybe i am doing something wrong or the option is present? I remember some problems like that in the past, but now they happens almost on always change.

Keazen oplossing

Hi Xixo.

I would advise you to just use Ctrl+F5 shortcut instead, which should work in all browsers to reload the page bypassing cache. Or you can just disable cache (set it to 0 MB) in Firefox in Settings > Advanced > Network tab.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (7)

more options

Keazen oplossing

Hi Xixo.

I would advise you to just use Ctrl+F5 shortcut instead, which should work in all browsers to reload the page bypassing cache. Or you can just disable cache (set it to 0 MB) in Firefox in Settings > Advanced > Network tab.

more options

If you change the content, but leave the file (image) names the same then consider to add extra GET parameters like a date-time string to the URL to make each file unique.

more options

The answer of Michal Stanke seems working. Anyway, I would expect that as default for Firefox Developer Edition, because I suppose it's a common need for developers.

more options

Ctrl+F5 works the same way as Ctrl+Shift+R and bypasses the cache, so both should work. You may have to use it more than once.

See also:

more options

cor-el said

You may have to use it more than once.

That's the problem actually (did i press that enought times?).

The link you gave about browser.cache.check_doc_frequency seems quite interesting, i will try to set its value to 1.

more options

<snark>Cleaning the cash... is that like laundering money? </snark>

more options

Narvey said

<snark>Cleaning the cash... is that like laundering money? </snark>

You know, in English the pronuciation and the writing is not always logically related... so may be :)

Bewurke troch Xixo op