Every website is accessible to anyone in the world. Unfortunately, some of those people might want to malicious mess with your website. Some people might want to steal financial data, others might just want to damage your companies brand. This section discusses the threats that people might use to target your website and how to configure Episerver to prevent anyone doing anything you don’t want them to.
Adding in Output Caching Globally On All Controllers
First off, you can enable global 'OutputCacheAttribute ' to cache all of your controllers. This approach is a bit more flexible than having to add it to each action on your site, as recommended i[...]
The EPiServer API does a lot of caching in the background to help improve your website's performance. This is one of the main reasons Episerver API works so quickly. It also makes the developers' lives easier as it is normally one less thing to worry[...]
When it comes to improving the performance of your website, performance optimisation is kind of a dark arts subject. One thing that is usually a given, is that if you try and need to do something custom then you're probably in for an interesting jour[...]
In the first post, I talked about enabling the output cache in your Episerver website to get the benefit of HTML caching in your solution in , http://jondjones.com/learn-episerver-cms/episerver-developers-guide/episerver-caching/episerver-caching-the[...]
In the previous articles I've talked about how to use the Output cache to cache objects in your website. When applying an output caching strategy there are several paths that you can consider:
Full Page Caching
In a full page solution, you use the[...]
This is the fourth post in a series of posts covering Episerver output caching; I would recommend reading Episerver Caching - Output Caching Strategies Explained.... What Is a Donut Cache? to understand some of the needs as to why you might want to c[...]
In any high load website, how you deal with your cache is kinda important. In most website scenarios, you might consider using the out-of-box output cache provider with memory cache and for the majority of projects this is more than adequate; on som[...]
This is the fifth post in my series covering output caching in Episerver. As the number of posts implies, caching in Episerver can be complicated. In the previous guides, we've talked about when and why you may not use 'full page' caching and why you[...]
This is my second post regarding Redis. In How To Implement Redis With Episerver Easily . In my last post, I talked about the benefits of using Redis as a session state provider and a cache manager.
To recap the article, Redis provides a persistence[...]
A semi-common Episerver requirement is to have a staging/live configuration. In this type of environment three servers exist, one server behind a firewall with the Episerver editor enabled and two loads balanced web facing boxes that have Episerver d[...]
Having a performant website will be the top of most clients' lists of things to do and one technique that you can employ to speed your website up is cache busting on the Episerver assets on your website.
Getting the balance of what to cache and how [...]