CloudFlare makes caching easy. Our service automatically determines what files to cache based on file extensions. Performance benefits kick in automatically. For customers that want advanced caching, beyond the defaults, we have Cache Everything available as Page Rules. Designate a URL and CloudFlare will cache everything, including HTML, out at
(Image credit: markyharky) This is the first in a series of posts looking at what makes the web slow and what to do about it. Suppose you needed to transfer 1TB of data (perhaps your home movie collection) from San Francisco to London. What would be the fastest route? Put
On Monday, CloudFlare officially announced Page Rules. The new feature allows you to customize behavior on a page-by-page basis. The previous two blog posts have outlined how you can turn off CloudFlare's features based on URL patterns, or accomplish advanced URL forwarding. In addition to the ability to
CloudFlare gets a lot of questions about caching and our free CDN (content delivery network), so I thought I would put together a really quick guide about what CloudFlare caches and more. Why should I cache my static content at all? Distributing your static content with CloudFlare's CDN
Many of our recent blog posts have had to do with helping customers navigate the CloudFlare service effectively. Staying with that theme, we wanted to review some of the most frequently used CloudFlare settings that people use (or need to know about) on the CloudFlare 'Settings' page. CloudFlare
Caching is great. CloudFlare makes sites faster in part by taking the static portions of your site and moving them closer to the visitors to your site. CloudFlare is smart about only caching static objects so you can run a dynamic, database-driven site and it will behave as you expect.