Impersonate Login Page

[PokerJoker]

My company has a third party purchased website that we use to allow clients
to log in and view/modify orders in our system.

It has its own login page, but I would like to add a form to my companies
own website to post the login directly (for client conveniance reasons).

Below is the code that I'm attempting to use, the post seems to be working
fine, but I'm getting an error back that "WebTrac Pro is not available at
this time, Please contact your administrator or check the log for details"
(the log is empty).

I'm wondering if maybe they are explicitly checking "where" the login
attempt is coming from and blocking it if it isn't what they expect? Is this
a common practice?

Here is the code:

-----------
Dim stringPost = Request.Form.To String

Dim httpWebRequest As System.Net.Http WebRequest =
System.Net.Http WebRequest.Crea te("https://web.hmic.com/webtracpro/ModelDriver.asp x")

httpWebRequest. Method = "POST"

httpWebRequest. ContentLength = stringPost.Leng th

httpWebRequest. ContentType = "applicatio n/x-www-form-urlencoded"

Dim streamWriter = New
System.IO.Strea mWriter(httpWeb Request.GetRequ estStream())

streamWriter.Wr ite(stringPost)

streamWriter.Cl ose()

Dim httpWebResponse As System.Net.Http WebResponse =
httpWebRequest. GetResponse()

Dim streamReader = New
System.IO.Strea mReader(httpWeb Response.GetRes ponseStream())

Dim stringResult = streamReader.Re adToEnd()

streamReader.Cl ose()

Response.Write( stringResult)
---------

[Scott Allen]

On Mon, 15 Aug 2005 10:13:07 -0700, "PokerJoker "
<Po********@dis cussions.micros oft.com> wrote:

I'm wondering if maybe they are explicitly checking "where" the login
attempt is coming from and blocking it if it isn't what they expect? Is this
a common practice?

I'd suggest using Fiddler [1] to compare what your code sends to the
web site with what a web browser sends. Sometimes it's the littlest
things that make the difference, for instance, I've come across more
than one site that checks the user agent string. If the sites didn't
recognize the user agent they'd simply return a 404 or a 500 code. You
can set your own user agent string to make your request look like an
IE request with the UserAgent property on HttpWebRequest.

[1] http://www.fiddlertool.com/fiddler/

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/