Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

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

  • 1 wótegrono
  • 1 ma toś ten problem
  • 8 naglědow
  • Slědne wótegrono wót 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šykne wótegrona (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