|
Subject:
|
msxml3.dll error '80072f78'
|
|
Posted By:
|
looc
|
Post Date:
|
10/24/2003 3:45:16 AM
|
Hi
I´m having truble with msxml3.
I have an asp page that post to a cgi-script on a apache
server.
The cgi-script is on a selfsigned SSL page.
It works fine most of the time but if i dont use the page
fore some tim then try to use it i get
msxml3.dll error '80072f78'
The server returned an invalid or unrecognized response
if i reload it works again.
My asp server is a win 2003 server so i should have all
the latest sp for msxml.
i dont get the error everytime so it´s hard to reproduce.
Any one got any idea?
/bjorn
My code looks like this.
Dim myhttp
Set myhttp = Server.CreateObject("MSXML2.ServerXMLHTTP")
myhttp.setOption(2) = (myhttp.getOption(2) -
SXH_SERVER_CERT_IGNORE_ALL_SERVER_ERRORS )
strxmlurl="http://myserver.xx.xx/cgi-
bin/setPasswd?username=xx"
myhttp.open "GET", strxmlurl, False
myhttp.send
set strxml=myhttp.responseXml ' get the XMLDOM object
Set root = strxml.documentElement
RESULT = strxml.getElementsByTagName("RESULT").item
(0).text
|
|
Reply By:
|
mcbeev
|
Reply Date:
|
12/10/2003 5:36:55 PM
|
Im getting the same thing, ever find a solution?
|
|
Reply By:
|
binarysurgeon
|
Reply Date:
|
9/21/2004 8:35:33 PM
|
Any update with this? I am having similar problems with Win 2003 connecting to an Apache PHP script. My code is similar and I've tried connecting to Apache SSL servers using multiple CAs.
The problem happens randomly but enough to cause problems. Thanks for any help you can provide.
|
|
Reply By:
|
binarysurgeon
|
Reply Date:
|
9/24/2004 2:46:05 PM
|
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.
|
