To anyone who has used the new Application Initialization with IIS 7.5, have you ever found it to call a domain name other than localhost, when it calls the page listed in the initializationPage value? Even when it's configured for a site other than the"default web site"?
For instance, I have a site named xyz, and its initializationPage value is "startup.abc" (not the real extension, but it's not relevant and could lead readers to misapprehend an explanation).
Yet, when I watch a monitor for the web application handling those .abc requests, I can see that when the initpage is executed, the URL generated by IIS is nothttp://xyz/startup.abc but rather http://localhost/startup.abc (and indeed, the monitor also confirms that the user-agent of the request is "IIS Application Initialization Warmup".
So what does it take to get things to work correctly? I have not found anyone else reporting it, but I almost wonder if most people who report that "it's not working" are suffering the same problem--but they are confused into thinking it's not calling their intended page because perhaps they have no monitor that can confirm the actual page executed.
And for what it's worth, the requests are NOT logged in the IIS logs. That doesn't surprise me as much, since resources on the feature do say that IIS throws away the page output (of the page called as the initializationPage).
But if anyone has any thoughts on what could help me solve this (or can confirm if they see other than localhost called for their background init page) I'd appreciate hearing from you.