This warm-up occurs during startup of the IIS service (if you configured the IIS application pool as ) and when an IIS worker process recycles.
During recycle, the old IIS worker process continues to execute requests until the newly spawned worker process is fully warmed up, so that applications experience no interruptions or other issues due to unprimed caches.
The built-in request validation returns an error only when it finds the most common strings used in XSS attacks.
It is common practice in Web applications to move pages and other content around over time, which can lead to an accumulation of stale links in search engines. NET, developers have traditionally handled requests to old URLs by using by using the Search engines and other user agents that recognize permanent redirects will store the new URL that is associated with the content, which eliminates the unnecessary round trip made by the browser for temporary redirects. NET provides two default options for storing session state across a Web farm: a session-state provider that invokes an out-of-process session-state server, and a session-state provider that stores data in a Microsoft SQL Server database.
Some Web applications need to load large amounts of data or perform expensive initialization processing before serving the first request. NET, for these situations you had to devise custom approaches to "wake up" an ASP.
NET application and then run initialization code during the that directly addresses this scenario is available when ASP. The auto-start feature provides a controlled approach for starting up an application pool, initializing an ASP. Note IIS Application Warm-Up Module for IIS 7.5 The IIS team has released the first beta test version of the Application Warm-Up Module for IIS 7.5.
file to determine which Web applications need to be automatically started.
For each application that is marked for auto-start, IIS7.5 sends a request to ASP. NET 4, you now have a well-defined approach for performing expensive application initialization prior to processing the first HTTP request.