View Single Post
  #4 (permalink)  
Old September 24th, 2004, 02:46 PM
binarysurgeon binarysurgeon is offline
Registered User
 
Join Date: Sep 2004
Location: , , .
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I believe we found a fix for this. We were having random problems connecting to a script on an Apache web server via SSL. Apache has created a fix to deal with some Microsoft SSL connection problem in Internet Explorer (see http://httpd.apache.org/docs-2.1/ssl/ssl_faq.html#msie). It is handled by adding the following to your apache configuration file:

SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0

The XML component used in ASP must use the same SSL connection/handshaking code and has a similar problem, however, the UserAgent (which is used to fix this bug in apache) does not contain the phrase "MSIE". Therefore, we were able to prevent this problem by adding the following to our apache conf (in addition to the statement above):

SetEnvIf User-Agent ".*WinHttp.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0

The UserAgent passed by the XML code is "Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)". Therefore we picked WinHttp to be used for the detection of the XML connection.

We have being running for a few hours without a problem (we usually have problems within minutes). I'm not completely convinced this did the trick but I'm crossing my fingers. I know this doesn't solve the problem for people who are connecting to Apache webservers outside of their control but hopefully this helps some.



Reply With Quote