Although, no-cache alone should now work it is possible that visitors to your site will be running affected versions of Firefox. UPDATE: The lack of no-cache support is limited to early versions of Firefox 3.0 and was caused by a bug. These two header values can be combined to get the required effect on both IE and Firefox:Īs shown here in the HttpWatch header tab: This header also prevents reuse of the cached version of the page and triggers an HTTP GET if the page is navigated to using the Back button. The following response header in Firefox prevents persistent caching, by forcing the page into the in-memory cache: However, you can control where the page is cached and whether the cached entry can be used for display purposes. Firefox relies on having a copy of every page in the cache for commands such as File->Save As and View Page Source. So how can caching be turned off in Firefox? The simple answer is that it cannot. Also, if the page is reached using the Back button there’s no round-trip to the server and Firefox simple re-loads the page directly from the cache. It just means that Firefox will never read the page from the cache during a normal visit unless it has been re-validated by sending a GET request. However, this response header doesn’t prevent caching in Firefox. Of course, we always redirect POST requests to a GET to avoid breaking the Back button.
Here’s an example in the HttpWatch online store where we show that an order has already been processed if you click on Submit button followed by the Back button: Pages that use this header aren’t stored in the cache and IE will always reload them from the server even if you use the Back button to reach them. You can prevent any caching in IE by simply setting this response header: Using no-cache Doesn’t Stop Caching in Firefox
The rest of this post covers two important differences in Firefox that the affect caching of HTML pages. Static HTML pages, such as contact pages, FAQs or sitemaps, can make use of caching if they have a Last-Modified response header allowing the brower to revalidate them as required.For example, pages showing the state of a bank account or online order. Sometimes dynamic HTML pages need to be fetched from the server whenever they are displayed – even when the back button is used.In the previous post, we broke item 1) down into: The use of long expiration times (item 2 above) still directly applies to Firefox but there are some subtle differences in the configuration of item 1. Now that HttpWatch 6.0 supports Firefox we wanted to cover some differences in the way that it handles caching compared to Internet Explorer.
Firefox refresh page no cache how to#
This caching scheme is covered in Two Simple Rules for HTTP Caching along with some ideas about how to manage changes. images, CSS, Javascript) to expire at some distance time in the future. HTML resources are expired immediately so that any changes made to a site are quickly picked up by existing users.When you setup a web server there are generally two types of caching that you need to configure: The problem is, not all users know these options, and some just want a simple "Reset" button that they can click on with the mouse without having to use the keyboard.Two Important Differences between Firefox and IE Caching Redraw without caching Cut the address from the address bar, Paste it back into the address bar, press ENTER Redraw without caching Press form "Reset" button while holding SHIFT Fortunately, there are ways around this behavior if you are willing to use one of the "redraw without caching" options below: redraw without caching Press CTRL+F5 When you have a page that includes an HTML form, and you refresh/reload the page or use the back button, Firefox is kind enough to repopulate your inputs with what was entered before you navigated away.įor some use-cases, this is not the desired functionality.
0 kommentar(er)
