I write only to comment that you can support more connections if you serve
pages through https BUT images from http.
(You'll remember many https pages where the browser warms you something like
this page contains insecure elements or something similar...
from the old benchmarks Remy and I ran, 20
yup, you sure can if you're willing to subject the users to the annoying message. What
some people do is get a dedicated image server and setup https on it. that way, you
don't get the annoying warning and you don't impact the webserver doing the real work.
peter
Gabi [EMAIL PROTECTED]
Is there any way to optimize Tomcat's SSL implementation?
Can I change the protocol to only use 40 bit encryption?
Can I change the default keep alive time for the SSL session?
Are there any other values for 'protocol' other than TLS?
I am running a web app that is using Axis for web service
the good news is there's nothing much you can do to optimize tomcat's SSL. The bad
news is SSL is CPU intensive. the most reliable way to improve SSL performance is to
get a hardware accelerator. People tend to disagree on this, but I am biased in favor
of using hardware acceleration.
We use Apache HTTP on the front for SSL. Makes a world of difference.
Cheers,
Alex.
Jeremy Conner wrote:
Is there any way to optimize Tomcat's SSL implementation?
Can I change the protocol to only use 40 bit encryption?
Can I change the default keep alive time for the SSL session?
Are there any
