#View mozilla private cache code#

You can use this for CSS, favicons and what ever gets cached.

If it changes it will serve the new file (YES ALWAYS) because the browser get's a complete new URL and just believes that file is so new he must go get it. So cache will work normally if the number does not change. And however you include your files you can set that number via a timestamp when the js-file has last been modified. So now if you make changes you just have to change the number 1111111111 to whatever number you want. However, when it comes to where that actually is on disk, I hit a dead end because the file names are obscured. So what this does is, it kind of removes the 1111111111 from the path and links to the correct path. You can find the original URL of a cached file, information about the file, and the raw data, by opening the about:cache page (type or paste about:cache into the address bar and press Enter to open it). To make it work you need to add one or a few lines to your. So normally the script tag would look like: js files are placed in /my-site/some/path/ui/js/myfile.js ChromeCacheView - Cache viewer for Google Chrome Web browser VideoCacheView - Allows you to extract video files from the cache of your Web browser. Var value = document.getElementsByName('clear-browser-cache') Scripts = document.getElementsByTagName('script') Links = document.getElementsByTagName('link'),

#View mozilla private cache code#

The code below should be put in the 'js' folder with the name 'clear-browser-cache.js' Using SSL also makes some browsers not use caching unless explicitly told to. If you aren't using SSL, anyone with access to the network can sniff network traffic and easily see what your user is seeing. Regardless, I would like to point out that if you are working with sensitive data you should be using SSL. Most browsers have at least basic cache management settings where, at a minimum, you can choose how much space youd like the browser to use for its cache. You might also want to consider turning off auto-complete on form fields, although I'm afraid there's a standard way to do it ( see this question). You can find the original URL of a cached file, information about the file, and the raw data, by opening the about:cache page (type or paste about:cache into the address bar and press Enter to open it). What you can do is to tell it not to cache your page, by sending the appropriate headers or using these meta tags: This could be very easily abused - the minute a browser supports such a 'feature' will be the minute I uninstall it from my computer. It would be a huge security issue if that were possible. (thanks, no way a browser will let you clear its cache. Intermediate caches may still have the data cached though and may not respect the header. 2023 update: See the Clear-Site-Data HTTP header, through which the server can instruct a client web browser to clear the website cache for its domain/subdomain, regardless of earlier Cache-Control headers.