How is a browser on the Internet going to contact your internal CA to
validate the certificates? That timeout would be your problem.
You may want to use SSLDiag and see if anything is wrong with your
configuration from a functionality perspective. Performance perspective, I
suggest you use legitimate SSL Certificates (get trial Verisign/Thawte
certificates) and you should see comparable performance. SSL means a lot
more than just "encryption", and IIS fully supports SSL in a performant
manner.
http://www.microsoft.com/downloads/details.aspx?FamilyID=cabea1d0-5a10...bc-83d4
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Scott" <scott DeleteThis @mds.com.tw> wrote in message
news:eMApVG%23vEHA.4028@TK2MSFTNGP15.phx.gbl...
Does anyone who can help me to figure the following problem:
First I set my web site to accept https connection only.
It works in intranet is fine; however, when I try to connect it from
internet, it takes me almost 1 minute to handshake.
I've compared it with our another web site which designed by php in Apache.
I found both 2 are in the same condition, but different performance.
The web site in Apache processing Https connection is very faster, always
under 5 seconds.
We use internal CA to issue certification, not a public CA.
Am I doing something wrong or something configurations I didn't set?
I really need someone to help me!
Scott
FAQ
Profile
Private Messages
Log in
