problem with Microsoft.XMLHTTP post to an isapi dll

[Irene]

Hi,

I have an asp page that allows a user to search for info in a DB and
add info to a DB. The search uses "ADODB.Connection" objects in the
page, but the add will use a call to an isapi dll via the
"Microsoft.XMLHTTP" object. The results of the isapi dll will be
displayed to the user without refreshing the asp page.

I have a code snippet below for the isapi call. WHat is happening is
that the xmlhttp.responseText from the snippet below is empty after a
call to the isapi dll (the isapi dll is not getting hit). If I take
the url created below and stick it in a browser, I get the isapi
response that I expect. A subsequent call to the function below will
then succeed, but the isapi dll is still not getting hit. It seems
that the function will only succeed if there is a cached request (and
again, no interaction with isapi dll).

If anyone could look at the code below and let me know what I might be
doing wrong, I would greatly appreciate it.

Thanks in advance,
Irene

<script language="javascript">

function handleAddClick() {
var xmlhttp = new ActiveXObject ("Microsoft.XMLHTTP");

var url = "http://localhost/Scripts/isapiYYY.dll?VPAddCustomerOrder";
url = url + "&CustomerNum=" + document.theForm.custNo.value;
url = url + "&OrderNum=" + document.theForm.orderNo.value;
url = url + "&CustName=" + document.theForm.custName.value;
url = url + "&CustEmail=" + document.theForm.custEmail.value;

alert(url);

xmlhttp.Open("POST", url, false);
alert("opened the POST");
xmlhttp.Send();
alert("sent the request");
var resp = xmlhttp.responseText;
alert(resp);

}
</script>

[Bob Barrows]

Irene wrote:

Hi,

I have an asp page that allows a user to search for info in a DB and
add info to a DB. The search uses "ADODB.Connection" objects in the
page, but the add will use a call to an isapi dll via the
"Microsoft.XMLHTTP" object. The results of the isapi dll will be
displayed to the user without refreshing the asp page.

I have a code snippet below for the isapi call. WHat is happening is
that the xmlhttp.responseText from the snippet below is empty after a
call to the isapi dll (the isapi dll is not getting hit). If I take
the url created below and stick it in a browser, I get the isapi
response that I expect. A subsequent call to the function below will
then succeed, but the isapi dll is still not getting hit. It seems
that the function will only succeed if there is a cached request (and
again, no interaction with isapi dll).

If anyone could look at the code below and let me know what I might be
doing wrong, I would greatly appreciate it.

Thanks in advance,
Irene

<script language="javascript">

function handleAddClick() {
var xmlhttp = new ActiveXObject ("Microsoft.XMLHTTP");

var url =
"http://localhost/Scripts/isapiYYY.dll?VPAddCustomerOrder"; url = url

Where did you get the idea that you could submit directly to the isapi.dll?
I've always used xnlhttp to submit to an asp page on the server. I've never
seen an example of submitting directly to isapi.dll. Do you have a link to
some documentation stating that this is possible?

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Irene]

Hi Bob,

No, I have not seen any documentation for this. To be honest, I
thought that you could use different urls with xmlhttp, but the
example just happened to be for an asp page.

I first tried a real simple dummy example to make a request to the
isapi dll and get a response back, and that worked fine, so I assumed
I could do this (but now that I think of it, I may have tried the
request via the browser first and not realized that the asp request
was just using a cached result).

Are you saying that I cannot do this? If so, would you mind
explaining why? Please pardon my ignorance if it is something
obvious.

Thanks very much,
Irene


"Bob Barrows" <re******@NOyahoo.SPAMcom> wrote in message news:<ui**************@TK2MSFTNGP12.phx.gbl>...

Irene wrote:

Hi,

I have an asp page that allows a user to search for info in a DB and
add info to a DB. The search uses "ADODB.Connection" objects in the
page, but the add will use a call to an isapi dll via the
"Microsoft.XMLHTTP" object. The results of the isapi dll will be
displayed to the user without refreshing the asp page.

I have a code snippet below for the isapi call. WHat is happening is
that the xmlhttp.responseText from the snippet below is empty after a
call to the isapi dll (the isapi dll is not getting hit). If I take
the url created below and stick it in a browser, I get the isapi
response that I expect. A subsequent call to the function below will
then succeed, but the isapi dll is still not getting hit. It seems
that the function will only succeed if there is a cached request (and
again, no interaction with isapi dll).

If anyone could look at the code below and let me know what I might be
doing wrong, I would greatly appreciate it.

Thanks in advance,
Irene

<script language="javascript">

function handleAddClick() {
var xmlhttp = new ActiveXObject ("Microsoft.XMLHTTP");

var url =
"http://localhost/Scripts/isapiYYY.dll?VPAddCustomerOrder"; url = url

Where did you get the idea that you could submit directly to the isapi.dll?
I've always used xnlhttp to submit to an asp page on the server. I've never
seen an example of submitting directly to isapi.dll. Do you have a link to
some documentation stating that this is possible?

Bob Barrows

[Bob Barrows]

Irene wrote:

Hi Bob,

No, I have not seen any documentation for this. To be honest, I
thought that you could use different urls with xmlhttp, but the
example just happened to be for an asp page.

I first tried a real simple dummy example to make a request to the
isapi dll and get a response back, and that worked fine, so I assumed
I could do this (but now that I think of it, I may have tried the
request via the browser first and not realized that the asp request
was just using a cached result).

Are you saying that I cannot do this? If so, would you mind
explaining why? Please pardon my ignorance if it is something
obvious.

The destination url in the call to xmlhttp needs to be a destination that
can process a Request and return a Response. I.E., it has to be a url that
you can use in the action attribute of a FORM tag. AFAIK, only a .asp page
meets these requirements.

Now, if the isapi.dll meets these requirements, I guess there is no reason
it can't work in xmlhttp, but, I neither know of any reason it should work
nor any other reason beyond the above why it shouldn't.
Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Irene]

Hello,

I ended up changing the 'POST' in 'xmlhttp.Open("POST", url, false);'
to a 'GET' and it works now!

Thanks again for your responses.

Irene
"Bob Barrows" <re******@NOyahoo.SPAMcom> wrote in message news:<ej**************@TK2MSFTNGP10.phx.gbl>...

Irene wrote:

Hi Bob,

No, I have not seen any documentation for this. To be honest, I
thought that you could use different urls with xmlhttp, but the
example just happened to be for an asp page.

I first tried a real simple dummy example to make a request to the
isapi dll and get a response back, and that worked fine, so I assumed
I could do this (but now that I think of it, I may have tried the
request via the browser first and not realized that the asp request
was just using a cached result).

Are you saying that I cannot do this? If so, would you mind
explaining why? Please pardon my ignorance if it is something
obvious.

The destination url in the call to xmlhttp needs to be a destination that
can process a Request and return a Response. I.E., it has to be a url that
you can use in the action attribute of a FORM tag. AFAIK, only a .asp page
meets these requirements.

Now, if the isapi.dll meets these requirements, I guess there is no reason
it can't work in xmlhttp, but, I neither know of any reason it should work
nor any other reason beyond the above why it shouldn't.
Bob Barrows