IIS or web.config - How to use virtual path based on port number?

[fletchsod]

I'm trying to get this to work teh same way as Apache does. Here what I does is ...

--snip--
c:/website/testcase1/

http://www/default1.aspx

c:/website/testcase1/secure/default2.aspx
--snip--

I want the "www" directory to work in port 80 and "secure" directory to work in port 443.

So, when I type "

http://www.domain.com"

(or "

http://www.domain.com/default1.aspx"),

it would automatically use port 80 and use the "www" directory.

Again, when the "

https://www.domain.com"

(or "

https://www.domain.com/default2.aspx"),

it would automatically use port 443 and use the "secure" directory.

I couldn't for the life of me figure out how to do it with web.config?

I welcome some help as this is a bit confusing in IIS.

Thanks...

 

[mmaz]

This article explains nicely how to achieve the desired functionality in IIS:

http://weblogs.asp.net/pwilson/archive/2004/12/23/331455.aspx

Hope it helps!

 

[fletchsod]

That's a nice article. Thanks for providing the link...

After seeing lack of responses and lack of documentation, it get me thinking that this whole this isn't very common as Microsoft had claimed. (Microsoft claimed that most people are using IIS and Microsoft claimed it to be as easy as ABC).

So, I have been seriously thinking of migrating the website to Apache while keeping the ASP.NET source code intact. Apache makes things so easy for a more experience users and I get tired of doing all of the IIS's GUI thing only to forget when I come back later. The GUI seem to be a bit of a overhead if you have a lot of configuration there. With Apache, I can do lots of things with all of the features in the httpd.conf than I can with IIS. So, I have been seriously thinking of migrating the website to Apache to save me the trouble in the long run.