Client VBScript and Viewstate for ASP .NET Webpage

[Joseph Morales]

I'm trying to code a free-standing VBScript, executed by Windows Script Host
on a client system, to push a button on an ASP .NET webpage that is hosted
by another server. Note that the script is not part of a webpage and does
not execute in a web browser. Instead, the script uses Msxml2.XMLHTTP to
send an HTTP request. To figure out what to include in the request body, I
used a Proxy Trace utility and captured the data that is sent when you push
the button we want on the webpage in a browser. I was able to make a script
that works temporarily.

However, on subsequent days, the script stops working. I found that if I do
a Proxy Trace again, the Viewstate data in the body has changed. Why would
the Viewstate data be different on different occasions, if all the controls
on the form have the same values?

I asked the developer of the webpage, and he said they did not request
encryption not did they use the ViewStateUserKey. The Viewstate should be
behaving according to its defaults. Is there something that causes the
Viewstate to vary from session to session? If so, how can my client script
know what Viewstate data to pass?

Thanks!
--
Joseph Morales
[To reply directly, remove "deletethispart." from my E-mail address ]

[Bruce Barker]

the viewstate is varied on every page render, and the matching viewstate
must be posted. before posting a page, you should go a get, parse out the
viewstate and send it back. its encrypted so that client apps like yours can
not modifiy it.

-- bruce (sqlwork.com)


"Joseph Morales" <jo************@deletethispart.unisys.com> wrote in message
news:d4***********@si05.rsvl.unisys.com...

I'm trying to code a free-standing VBScript, executed by Windows Script
Host on a client system, to push a button on an ASP .NET webpage that is
hosted by another server. Note that the script is not part of a webpage
and does not execute in a web browser. Instead, the script uses
Msxml2.XMLHTTP to send an HTTP request. To figure out what to include in
the request body, I used a Proxy Trace utility and captured the data that
is sent when you push the button we want on the webpage in a browser. I
was able to make a script that works temporarily.

However, on subsequent days, the script stops working. I found that if I
do a Proxy Trace again, the Viewstate data in the body has changed. Why
would the Viewstate data be different on different occasions, if all the
controls on the form have the same values?

I asked the developer of the webpage, and he said they did not request
encryption not did they use the ViewStateUserKey. The Viewstate should be
behaving according to its defaults. Is there something that causes the
Viewstate to vary from session to session? If so, how can my client script
know what Viewstate data to pass?

Thanks!
--
Joseph Morales
[To reply directly, remove "deletethispart." from my E-mail address ]