Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Will reloading while ignoring the cache (ctrl+shift+R) always ignore the cache?

  • 1 wotmołwa
  • 1 ma tutón problem
  • 8 napohladow
  • Poslednja wotmołwa wot Pj

kbrockert
kbrockert
more options

I thought that the keyboard shortcut ctrl+shift+R always ignored the cache and responses were usually 200 rather than 304. However, I seem to be getting 304s every time I reload with any of the keyboard shortcuts. Could an update have broken these keyboard shortcuts? Or am I mistaken and the server can force you to use the cache on your local device?

I thought that the keyboard shortcut ctrl+shift+R always ignored the cache and responses were usually 200 rather than 304. However, I seem to be getting 304s every time I reload with any of the keyboard shortcuts. Could an update have broken these keyboard shortcuts? Or am I mistaken and the server can force you to use the cache on your local device?

Wšě wotmołwy (1)

Pj
Pj
more options

kbrockert said

I thought that the keyboard shortcut ctrl+shift+R always ignored the cache...

The only two functions I know of are 'Reload' and SHIFT-Reload. The latter forcing a fresh page, skipping/dumping the Cache.


~Pj