D
Dave H
First..
What object (on the client) should I be using these days?
var xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
or
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
or maybe something different?
I have some browsers that can't do this correctly. I'm doing:
--client---
var xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
xmlhttp.Open("POST","/App/PostTransactionASP.Aspx?Tran=Update&TranSubCode=xx
x", false);
xmlhttp.setRequestHeader("Content-Type",
"application/x-www-form-urlencoded");
xmlhttp.send(requestXML);
sResponseXML = xmlhttp.responseXML.xml;
--server--
Dim sTran, sTranSubCode
Dim oPost As New App.PostTransaction
Response.ContentType = "text/xml"
sTran = Request.QueryString("Tran")
sTranSubCode = Request.QueryString("TranSubCode")
Try
CallByName(oPost, sTran, CallType.Method, sTranSubCode)
Catch
Response.Write<Error>Error</Error>
Response.End
End Try
--------------------
Some browsers always get Error returned, like they're unable to do the
CallByName. Is there some security feature stopping this?
Or, maybe I should start doing these in a completely separate way? I really
like this mechanism, and have been using it internally for a few years, but
on these new client machines it's driving me nuts!
Thanks, Dave
What object (on the client) should I be using these days?
var xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
or
var xmlhttp = new ActiveXObject("Msxml2.XMLHTTP");
or maybe something different?
I have some browsers that can't do this correctly. I'm doing:
--client---
var xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
xmlhttp.Open("POST","/App/PostTransactionASP.Aspx?Tran=Update&TranSubCode=xx
x", false);
xmlhttp.setRequestHeader("Content-Type",
"application/x-www-form-urlencoded");
xmlhttp.send(requestXML);
sResponseXML = xmlhttp.responseXML.xml;
--server--
Dim sTran, sTranSubCode
Dim oPost As New App.PostTransaction
Response.ContentType = "text/xml"
sTran = Request.QueryString("Tran")
sTranSubCode = Request.QueryString("TranSubCode")
Try
CallByName(oPost, sTran, CallType.Method, sTranSubCode)
Catch
Response.Write<Error>Error</Error>
Response.End
End Try
--------------------
Some browsers always get Error returned, like they're unable to do the
CallByName. Is there some security feature stopping this?
Or, maybe I should start doing these in a completely separate way? I really
like this mechanism, and have been using it internally for a few years, but
on these new client machines it's driving me nuts!
Thanks, Dave