IIS 5 & IIS 6
IIS 6.0 & WS & HTTP Keep Alive
Last post Jul 11, 2007 02:35 PM by mvolo
Apr 22, 2007 02:41 AM|kolbis|LINK
I have a web service application at the backend and a driver at the front end. The driver consums the web service over SSL. I
want to tune up my IIS server machine, so here are the configurations that I defined:
Normally, if the IIS hosts a web service, the HTTP Keep Alive is not needed; however we run the web service over SSL. So, from
my understanding there are two round trips from the driver to the IIS for each request.
Is that true?
Does it depend on the user mode / kernel mode we use with the SSL?
ASP.NET Performance Wildcard
Jul 11, 2007 02:35 PM|mvolo|LINK
IIS6.0 provides built-in SSL support, so I am not sure why you require a separate driver to accept reqeuests over SSL. You can configure an IIS website to receive requests over SSL, and then host web services on it with ASP.NET 2.0 or WCF.
If you are making more then 1 request per session, you should be using keep-alives to make sure that the connection stays open - this will improve your web server's performance especially under load. For SSL, this is even more important since there is much
more overhead per connection. However, I do not believe that keep-alives are functionally required, since the SSL negotation happens underneath the http protocol.
Can you elborate more on you architecture / why you are using a separate driver?