Re: HTTP Communications with USBank/SSL Tracer?

[Scott Klement <klemscot@xxxxxxxxxxxx>]

I guess what I was trying to say is that you could try HTTPAPI, and if it
works, then you could look at how it's formatting the HTTP requests.  I
would've pointed you at my sockets tutorial if I thought you needed help
with sockets :)   I didn't, because I figured you needed help with HTTP.

The only other alternative that I can think of is to create a http to
https proxy, and connect to it with your normal web browser, see how it's
formatting the requests, and copy that.

That'd be a bit of programming (if you can't find an existing tool) but it
should get you results.



On Tue, 29 Oct 2002, Brad Stone wrote:

> > I haven't done this with USBank specifically, but I've
> > done it with
> > other sites, does that help?
> >
> > You might look at the code to my open-source HTTPAPI
> > project, which
> > does SSL and also does the username/password signon.
>
> Scott,
>
> I've got all the sockets stuff down.  It's just formatting
> the HTTP request that I seem to be having problems with, and
> why the server is returning to me a 500 Internal Server
> Error.  I assume it's because something is wrong with my
> HTTP request.
>
> I've tested it on similar sites with no problems.  I guess
> I'll just cross my fingers and wait for USBank to try and
> tell me what I may have done wrong.
>