Re: http_url_post_stmf Not Posting

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

302 usually is a "redirect".  You can get the location of the redirect 
by calling the http_redir_loc() API.  It should return the URL that 
they're telling you to redirect to.

You could then try to run an HTTP_url_get() on that location.

I wouldn't keep doing this in a "forever" loop, however.  The likelihood 
of an infinite loop is too high.  Instead, I'd let it redirect you 5 or 
10 times, and if it still isn't giving you the destination page, then 
spit out an error for the user.

The fact that it references an error with an ErrorDocument is highly 
suspect.  My guess is that it doesn't like the way you're sending some 
input to the page.  So, it's trying to re-direct you to an ErrorDocument 
(a page that explains an error).  Since that ErrorDocument isn't found, 
you get redirected...


daparnin@xxxxxxxxxxxxxx wrote:
>    Last week I posted a problem we are having sending a file to our bank.
>     It used to work then suddenly stopped.  By stopped I mean that our
>    file isn't uploaded to the web site.  The only thing that seems to be
>    different is that we are getting a 302 after the http_url_post_stmf.
>    What does one normally do in this situation?  Should the
>    http_url_post_stmf be repeated with the returned URL until we no
>    longer get a 302 similar to a  http_url_get?  Any thoughts or ideas
>    would be appreciated.
>    Dave Parnin
>    --
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------