Good morning,

I'm trying to adapt Scott Klement's HTTPAPI code to send a file to our
bank.  The digital certificate hurdle has been jumped but now I'm facing a
seemingly endless 302 redirect problem.  Ultimately I want to use Scott's
http_url_post() routine to fill in a box with a file name but have been
playing with the http_url_get() to try to resolve the redirection problem
so I can get to that point.

The scenario goes like this:
When I connect to http://www.bank.com/ it returns a 302 redirecting me to
http://www.bank.com/a.  When I connect to http://www.bank.com/a it returns
a 302 redirecting me to http://www.bank.com/b.  When I connect to that it
gives me a 302 that sends me back to http://www.bank.com/.  Argh!!!!  How
do I debug this?  I've looked at the files in /tmp but nothing has jumped
out at me.

>From a browser perspective I connect to http://www.bank.com, click the
login/logout button, and am taken to the page that I want to get to however
the address in the browser's address box doesn't change.  How can I tell
where my browser is pointed other than the address bar and viewing the
source of the initial page?  Any thoughts?

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx


HTML Source for first page:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Logged In</TITLE>
</HEAD>
<BODY>
<CENTER><A HREF="/" onMouseOver="window.status='Continue';return true"><IMG
SRC="/icons/stlogo.gif" BORDER=0 ALT="Continue"></A></CENTER>
<BR>
<HTML><P>
WARNING!  You have accessed a private computer system... blah, blah,
blah...
</P></HTML>
<BR>
</BODY>
</HTML>





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.