The two new additions in IIS 8 are
This setting is available if you have the Application Initialization module installed
The preloadEnabled metabase setting along with the startMode setting can be used to ‘warm up’ your web application.
When you set the startMode property of your application pool to AlwaysRunning a worker process is spawned as soon as IIS starts up and does not wait for the first user request. But this does not mean the web application is initialized.
When you set preloadEnabled to true, IIS will simulate a user request to the default page (can be changed with initializationPage metabase setting) of the website/virdir so that the application initializes. The request is not logged in the IIS logs.
But you can trace this with FREB. Every time you restart your application pool you will see a FREB trace file for the dummy request. You can identify this request by analysing the GENERAL_REQUEST_HEADERS and looking at the User-Agent string.
User-Agent: IIS Application Initialization Preload
Maximum Url Segments
With the maxUrlSegments metabase setting you can control the number of segments in an URL that your web application can serve. A segment is nothing but the number of / in your URL. This is a security setting that you can use to control the depth to which a user can browse your website.
So for example say you have an application whose URL are mostly of the format http://website/virdir/page, you can set the maxUrlSegments to 3. This stops probing attacks.
If a user tries to browse an URL with segments exceeding this limit he/she will see a 404 message and a 404.20 HTTP status code will be logged in the IIS logs.
What is this feature in aid of? What is it objective? That will help.Say it warms up a web application - what is that?
By design IIS does not start a web application until the first time someone requests a web page from it. The advantage of this is you could host dozens of web sites on your server & they will not use any resources if no-one is interested in looking at them. It may seem strange but heaps of sites are barely used.
1. If you have a WCF service inside IIS & it needs to pull messages off a queue. It will never start. So Autostart is brilliant here.
2. Some web sites maintain large caches which can take many seconds or minutes to fill. The first user to click on a page may get a really poor experience. So this feature can "Warm Up" the data cache. ie: Go the the database or other servers that supply the data the web site displays & store it in the Web sites memory (cache) in anticipation of the users request.