in reply to HTTP to FTP proxy

  1. You say you need to authenticate the users using client certificates. I assume that this does not mean that the FTP server requires it.
  2. The FTP protocol is implicitly file based (hence the 'F'). It only knows about files. You would need a client that had been modified (ok, hacked) to make the server believe it was getting a single file, while it was actually getting the data from the other connection. If the existing FTP server host is something you can modify, and you can run something like xinetd, it would be pretty easy to "roll your own" application to accept and store files.
  3. If you're stuck with FTP, but have the ability to have programs run on the FTP server (like via cron), you could file-buffer, eg filename.10meg.1, filename.10meg.2. You could write these files sequentially using FTP, then have a cron-based script look for filenames in this format and catenate them together after-the-fact.

    4. fnord

Replies are listed 'Best First'.
Re^2: HTTP to FTP proxy
by clumsyjedi (Acolyte) on Nov 19, 2010 at 12:08 UTC
    Not sure how to quote your comments sorry

    So...

    1. No, the FTP server is plain text username and password. The End user should not know these credentials.
    2. The protocol is for transferring files yes, but no local file is required to put a file on the remote server. The STOR command identifies the remote file name, the PORT or PASV commands identify network connections over which the data for that remote file should be read (this is my understanding anyway).
    3. No, I have no access to the remote machine, can't run code there. Can't change it's auth mechanisms. Can't do nuthin' :)
[reply]

In Section Seekers of Perl Wisdom