We actually have two web sites with the session state shared. One's the
secure version and the other is the normal version. They point to the same
directories and code. It really a mapping issue. However they are
distinctly different sites as far as Orion is concerned. So if you do any
caching of static items they will get loaded twice, one per site. So we do
a lot static singleton classes that have our caches, making the data
available throughout the JVM once.
There's a performance hit the first time you navigate to the first SSL
protected page but after that it gets better.
We haven't done measurements yet (that will be soon) but it is noticeably
slower running in SSL. Makes sense due to the computation efforts envolved
with encryption and all the CPU cycles stolen to handle the security.
So for best practices we try to SSL as little as possible to keep a high
throughput on the Web server.
So it sounds like you have a similar problem as we had so this solution
should help you.
MD
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin
Sent: Monday, September 25, 2000 10:34 AM
To: Orion-Interest
Subject: SSL - Only a few pages need SSL, does that slow things down?
Hi,
Seeing all this SSL talk has me wondering a bit...we only have 3 pages right
now that use the HTTPS protocol. The other 200+ are just HTTP. If we have
Orion use SSL does it take any noticeable hit on the rest of the pages that
are not using SSL? I just want to make sure that before we go production
with our clustered SSL Orion setup, it isn't going to come to a crawl
because a few pages are using SSL. I haven't read much on how to get SSL to
work yet, but it seems to me as if the whole server goes in to SSL mode if
you use it. Is this the case..or is it only pages that use SSL that are
slow, the rest being unscathed by the SSL mode?
Thanks.
