Better yet, since the content in the http and https sites sounds to be
mutually exclusive, consider putting the http site files into one folder,
the https files into another folder, and serve up the two folders as two
different virtual servers, one listening only for HTTP and one that requires
HTTPS for access.
I think the theoretical problem with writing your own script for such
security is that it is elegant and less simple, so more chance for something
to go wrong or for a security problem to occur as compared to using the
checkboxes in IIS and mingling the code into one common folder / server
instance.
[quoted text, click to view] "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:e01bZ$C5FHA.252@TK2MSFTNGP15.phx.gbl...
> Make the default page an ASP page, and write code in the page that checks
> if
> the request is over SSL or not. If not over SSL, just output the text page
> about the site. If over SSL, send page to do user login.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> <blasapher@cox.net> wrote in message
> news:1131431017.468306.260660@f14g2000cwb.googlegroups.com...
> First of all, I'm new here; and just now learning IIS - so thanks for
> being patient with me!
>
> I have a website,
www.mywebsite.com, that has default page of
> default.aspx.
>
> I have applied the SSL to the entire site.
>
> Now, my customer would like to be able to do this:
>
> They would like to go to
www.mywebsite.com and have a page come up
> (lets call it index.html) that is just a text page about the site.
> Then, for those people who know about the site; they can type the
>
https://www.mywebsite.com and the default page will launch and they can
> login to the database. How can I do this?
>
>
> Any input is appreciated!
> Steph
>
>