Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

In Firefox 5 Page is loaded from the BFCache instead of loading it from the server

more options

I employ Websphere's form based authentication for protecting my J2EE web application. In the previous Firefox versions when authenticated the requested protected page is fetched from the server and now in Firefox 5 the page is from the BFCache and it causes some abnormal behaviours in my application. But, i f i change the config parameters browser.cache.disk.enable and browser.cache.memory.enable the page is from the server.

It is impossible for me to ask my users to do this config stuff to access my application in Firefox 5.

Please let me know if there is a way to solve this issue.

I employ Websphere's form based authentication for protecting my J2EE web application. In the previous Firefox versions when authenticated the requested protected page is fetched from the server and now in Firefox 5 the page is from the BFCache and it causes some abnormal behaviours in my application. But, i f i change the config parameters '''browser.cache.disk.enable''' and '''browser.cache.memory.enable''' the page is from the server. It is impossible for me to ask my users to do this config stuff to access my application in Firefox 5. Please let me know if there is a way to solve this issue.

Все ответы (3)

more options

I'm not aware of any changes in this area, but that doesn't mean there aren't any...

Can you check the old article on this for suggestions?

https://developer.mozilla.org/en/using_firefox_1.5_caching

more options

I used both "no cache" and "no store" for cache-control header and still the page is not retrieved from the server and shown from the cache. Is there any other way to restrict firefox 5 to restrict from showing cached pages????

more options

Other than the methods mentioned in the article (headers, unload event handler), some people add an argument to the URL (e.g., a timestamp).