Once the page is compiled, the actual request processing begins. The page is instantiated and executed. The page and all controls on it go through their lifecycle to complete their business logic and generate the output HTML. Also, this is the stage where all permissions are checked, all necessary data is collected from the database etc. Once the response is generated, it could be cached before sending it to the client. By default, Sitefinity CMS caches the response allowing subsequent requests to skip the entire step.
NOTE: The response may vary for different browsers and some request conditions. This is why this step may still be executed even though the output has already been cached. For example, if the request is authenticated with credentials that allow inline editing, output cache will not take effect and this step will always be executed. When testing output cache, make sure you are logged out.
RECOMMENDATION: Configure the output cache, so that you ensure output cache is turned on for pages, has a longer duration time, and configure various output cache settings that affect performance. For more information, see Best practices: Configure output cache.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important