I may have located my problem (after many tries this weekend and use
of an HTTP sniffer program). It seems that I was setting variables
for the various fields just as they were on the web page. The
variables included things like %24 that HTTPsocket would transform to
%2524 when sending it to the server. So, I replaced the ascii codes
in the variables and the values with "$" and "/" or whatever was
appropriate.
I finally managed to get something besides an error page.
It is an interesting characteristic to be aware of when sending form
data through an HTTP socket.
Brad
On Feb 10, 2007, at 3:46 PM, Brad Taylor wrote:
I hope some of you can help me with a dilemma I am facing.
BACKGROUND
----
I have a published application that has a web page login where
users (that subscribe to a third party service) can automatically
log into the third party's web page and retrieve a simple data file
once logged in (a simple text file). Previously, the web server
used a standard HTML form for the member log in. Recently, the
third party changed to an ASP.NET server, and I am having trouble
getting the login to work again. (argh!)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
