Configuring IIS

[andegre]

I have a web application which is in ASP.NET 2.0 running on a server. When configuring the website on the "Web Site" tab, does it matter if I leave the IP address on (All Unassigned) or should I specify the IP address? If I don't specify, it appears that the service is looking for requests from two different locations (local server's IP address and also the NLB IP address). Could this possibly cause a performance problem since it's trying to watch 2 locations?

Thanks,
andegre

 

[TallOne]

I've been using IIS6 for my web app installs and I force SSL by selecting force ssl in the certificate edit. However if a user types the url http:// rather than https:// the user gets a 403.5 error. I circumvent this by using a custom error page the redirects to the desired page using

https://.

I thought I read somewhere that IIS7 resolves this, but as I look, I see similar solutions with the new addition(to me) of a custom httpmodule that basically does the same thing.
Questions: 1. Does IIS7 have a resolution for this? 2. What do you guys think about letting port 80 through anyways if the site is to be secured(I know users will type

http://www.domain.com

expecting to go to a secure site)?

 

[TallOne]

Andegre, Sorry about the previous post. I meant to create a post rather than reply. I believe in your case you will want to leave [All Unassigned]. I believe the selection is for configuring multiple websites host header records per ip address. Do you have host header records for each ip?