Hello Kevin,
This is in the docs, but what you need to do except for pure SSL settings is
that you copy the default-web-site.xml file to another name and add
secure="true" to the web-site tag of the new file.
So, yes, you need to do something.
However, normally you want to present different applications and content on the
secure site and not just a copy of your normal site (entering your credit card
info should probably only be available on HTTPS for example) and then of course
you need to reference in the web-site.xml that it will serve other
web-applications.
Regards,
Karl Avedal
"Duffey, Kevin" wrote:
> Hi Karl (and all),
>
> > HTTPS listens to another port than HTTP does. The default is
> > that HTTPS listens
> > to 443 while 80 is used for HTTP, so the URLs https://www.foo.com and
> > http://www.foo.com access different ports. If you run HTTPS
> > on port 80 you need
> > to access it through https://www.foo.com:80.
> >
> > You do not run HTTPS and HTTP on the same port in either Orion or IIS.
>
> Ok..this I understand. However, what I am getting at is on our current
> setup, IIS/JRUN, we have IIS with a certificate..set up on port 443.
> However, when I make a request to a page, I simply put in
> https://www.domain.com/page.jsp On the server side, I don't have to do
> anything extra with IIS or JRUN, other than the IIS certificate setup, to
> get it to make those pages secure. Someone on this list said I would
> probably have to put all my secure pages in a completely separate web-app
> tied to port 443 to make them secure under Orion. That is what I need to
> know. Do I have to do anything extra that I am not doing now, other than the
> certificate process, to get my pages located in the same dir (and web-app)
> that need to be secure? Or can I just install the certificate somehow, and
> all is hunky dory?
>
> Thanks.
