Caching CSS & JavaScript using Rewrite Rules in IIS6
Recently I’ve been working on improving the caching within the website at Huddle to improve performance for users. After reading around, I found the following rules to be valuable.
- Cache your CSS and JavaScript forever (set a long, long expiry)
- Handle updates by changing the URL of your CSS and JavaScript
When caching “forever” the main problem is if you release an update to “styles.css” the browser caches the URL of that file, but won’t pick up any future updates unless the user clears their browser cache (you don’t want to have to tell people to “Ctrl + F5″). By changing the URL of the file, the browser thinks it’s requesting a new file, and your updates get applied. But how do you go about doing this without it becoming a pain to manage?
Securely Deleting Files in Ubuntu
*Update – the below article applies for installing nautilus-actions, but I have since updated my shred action.
Simply pressing delete on a file or folder won’t remove it from your hard drive. The reference will be removed from the file system but it will still exist on your hard drive until the space it occupies is used and it is overwritten. This can pose a problem as people can recover potentially sensitive information.
There’s an application called “shred” (installed by default) in Ubuntu for securely deleting files. It overwrites where the file is located many times, ensuring it can’t be recovered. Shred can be integrated into Nautilus easily using Nautilus Actions.
Setting up Ubuntu Hardy Heron
Recent Photos
