I know that IIS versions 7.5 and earlier do not support wildcard host header bindings.
Have they added it in the latest version (8.5)? I see that it finally supports SNI and wildcard binding (*.mydomain.com) seems like it would be a related feature.
I'm trying to debug/verify my web.config for an ASP.Net MVC 3 application running on IIS 7.5.
When a request comes in, it gets ran through the stack of configured HttpModules and finally gets delivered to a particular HttpHander. I need a way to run a request, then log/view ALL of the modules that ran and which handler actually received the request. INCLUDING the modules/handlers built in to IIS, not just my custom ones.
The reason I want this is I have reason to believe that the session state module is running for static files. I want to verify that I've got that fixed plus make sure nothing else funny is going on with my static files like forms auth module for example.
My app is running in integrated mode.
Microsoft's Web Platform Installer includes an item titled:
Recommended Server Configuration for Web Hosting Providers
This sounds handy, but I'm not about to install it without knowing what sort of configuration changes it makes. Could someone explain or provide a link to what bits this flips? My google-fu is usually strong, but I've not been able to find much about it.
I have a .Net web site with both public and private areas. The private sections are protected with .Net forms authentication. This all works fine. Site runs in IIS integrated mode.
My question is related to my QA/Test site we push changes to prior to going live. I don't want the general public or googlebot to have access to the QA site at all. Not even the portions that would ordinarily not require authentication to access.
The QA site does need to be accessible on the wild internet because we do want folks from other companies, etc. to be able to see and test changes before they go live. So my idea was to put a gatekeeper username/password in front of the entire site. Once people are past that door, they should have access to the "public" areas of the site. Accessing the member area would still require them to go through the forms auth as usual.
I tried turning off anonymous authentication and enabling basic auth, but I get an error about not being able to use 401 challenge based and redirected based auth simultaneously. Unfortunately that is exactly what I want.
I probably could write a custom HttpModule, but I'd rather just do it with standard IIS settings. Anyone have any ideas on how to solve this?