Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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ć.

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

Don't firefox ofusers of my site cache my site pages

  • 3 wotmołwy
  • 9 ma tutón problem
  • 5 napohladow
  • Poslednja wotmołwa wot guigs

more options

HTTP Header

Cache-Control: private, no-cache, no-store, must-revalidate

was used but still caching the page.  I can view even authenticated pages by using work offline.

please help

HTTP Header Cache-Control: private, no-cache, no-store, must-revalidate was used but still caching the page. I can view even authenticated pages by using work offline. please <b>help

Wšě wotmołwy (3)

more options

Hi intercept0r,

I'm sending this to our senior tech guys to see if there is something they can help with.

more options

HI,

I have posted the same. with my another ID That may help you to understand my problem in a better way. https://support.mozilla.org/en-US/questions/997007#answer-564691 Thanks Prasant Sharma

more options

Hi intercept0r,

Please run some tests with this add on Modify Headers with your site. I think that this may have to do with that you have put all of the parameters with no specifications.

For example: Cache-Control "max-age=3600, must-revalidate" must revalidate usually needs a time set

Check out this for more details http://www.mobify.com/blog/beginners-guide-to-http-cache-header...

However it may also be that we can test in the Web Inspector what may be changing from the response header to the no-cache, no-store headers.

I look forward to your reply!