You create a custom output-cache provider as a class that derives from the new .
For example, it is now possible to cache the "Top 10" pages of a site in memory, while caching pages that get lower traffic on disk.
Alternatively, you can cache every vary-by combination for a rendered page, but use a distributed cache so that the memory consumption is offloaded from front-end Web servers.
NET 4 to start the application in a state during which the application temporarily does not accept HTTP requests. NET instantiates the type defined by the method and the method returns, the ASP. For example, you can use the new auto-start feature to initialize an application and then signal a load-balancer that the application was initialized and ready to accept HTTP traffic.
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.
The built-in request validation returns an error only when it finds the most common strings used in XSS attacks.
Previous attempts to make the XSS validation more aggressive resulted in too many false positives.
Output-cache providers can use any storage mechanism to persist HTML content.
This makes it possible to create custom output-cache providers for diverse persistence mechanisms, which can include local or remote disks, cloud storage, and distributed cache engines.
NET 4 introduces a number of features that improve core ASP.