Re: FTPAPI

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>


You'll have to create a stream file that's multipart/form-data encoded.
HTTPAPI has routines for URL Encoding, but not multipart/form-data (yet)

Once you have that space created, you can upload them with the
http_url_post_stmf() routine in HTTPAPI.

I wrote some info about this to Dave Parnin a few weeks ago. Here's a link
to that message:
  http://www.scottklement.com/archives/ftpapi/200408/msg00001.html

---
Scott Klement  http://www.scottklement.com




On Tue, 24 Aug 2004, Elbert Cook wrote:

> Sender: "Elbert Cook" <elbert@xxxxxxxxxxxxxxx>
>
> Still can't get the FTP connection to work. The bank says its the way they
> NAT and that I'm probably out of luck.
>
> However I found out they have a https website for uploading and downloading
> files.
>
> I've downloaded the beta version of HTTPAPI and I'm playing with it.
> I have successfully logged-on and logged-off from the bank and I'm ready to
> try uploading a file.
>
> But I'm not sure of how to upload a file.
>
> Decoding their webpage I have.
>
> <form METHOD="POST" ENCTYPE="multipart/form-data"
> ACTION="/servlet/MailboxServlet"
> <input TYPE="HIDDEN" NAME="operation" VALUE="UPLOAD">
> <input type="radio" name="data_format" value="A" checked>
> <input type="FILE" name="sourcefile" value="testfile" size="25"
> maxlength="1024">
>
> Do I post the filename, or the file data, do I use the url_post_stmf
> command?
>
> POST  'https://www.abc.com/servlet/MailboxServlet'
> with parms 'operation=UPLOAD&data_format=A&sourcefile= {Filename or the
> ascii file data}'
>
> Prehaps I'm completely missing the boat on how an upload works.
>
> Sorry for all the novice question,
>
>
> ----- Original Message -----
> From: "Scott Klement" <klemscot@xxxxxxxxxxxx>
> To: <ftpapi@xxxxxxxxxxxxx>
> Sent: Monday, August 23, 2004 12:09 PM
> Subject: Re: FTPAPI
>
>
> > Sender: Scott Klement <klemscot@xxxxxxxxxxxx>
> >
> >
> > Hi Elbert,
> >
> > > I connect to their FTP server and get a secure connection on port 20021.
> > > I supply or userid and password.
> > >
> > > If I do a DIR or PUT, the connection eventually times-out.
> >
> > This is a firewall issue.    Each time you try to do a "DIR" or "LS" or
> > transfer a file (either PUT or GET) it makes a separate connection to the
> > server.
> >
> > In passive mode, the server tells the FTP program what port to connect to,
> > and then the FTP program connects to the server's port, receives/sends the
> > file or directory list, and disconnects.
> >
> > In standard (non-passive, or "active") mode FTP, the client actually sends
> > a port number to the server, and the server makes a connection back to the
> > client.
> >
> > Your firewall isn't allowing these connections through, and that's why the
> > timeout is occurring.
> >
> > To troubleshoot this further.
> >
> > a) Start an FTP session.  After you've typed the userid and password, type
> >     DEBUG 1
> >
> > b) type DIR.  It should show something like this:
> >
> >   > DIR
> >     >>> PASV
> >     227 Entering Passive Mode (192,168,5,7,192,0)
> >
> >   The word "PASV" means that you're working in passive mode.
> >   The numbers in parenthesis are the IP address and port that the client
> >   is attempting to connect to.   In this example, the IP address is
> >   192.168.5.7.  It should be the same address as the FTP server.  The
> >   final numbers are the two bytes that make up the port number.
> >   192 * 256 + 0 = 49152, so it's attempting to connect to port 49152 on
> >   the FTP server.
> >
> > c) Here's a standard FTP example of the same thing:
> >
> >  > dir
> >    >>> PORT 192,168,5,4,55,157
> >    200 PORT command successful.
> >
> >  In standard FTP, the FTP client is sending an IP address and port and it
> >  expects the server to connect back.  So this time, it'll be an INCOMING
> >  firewall rule that needs to be added (which is why passive is the
> >  default, so that people don't need to open more incoming ports)
> >
> >  the number following the "PORT" subcommand is, again, the IP addess
> >  followed by 2 bytes for the port. In this case, the port is
> >  55 * 256 + 157 = 14237
> >
> > The really fun part about it is that the port number can/will be different
> > with every file transfer or directory listing.  Usually, there's a range
> > of port numbers that's used, but on a busy FTP server, that can be a very
> > large range.
> >
> > Good Luck
> >
> > -----------------------------------------------------------------------
> > This is the FTPAPI mailing list.  To unsubsribe from the list send mail
> > to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> > -----------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubsribe from the list send mail
> to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> -----------------------------------------------------------------------
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------