SSL File Transfer

Fairlight fairlite at fairlite.com
Thu Dec 9 11:19:27 PST 2004


At Thu, Dec 09, 2004 at 09:33:07AM -0500 or thereabouts, 
suspect lists at harris-home.com was observed uttering:
> Ok let me clarify. I'm not expecting anything magical here. Just a file
> transfer. ;)

Heh...you're dealing with a spec that has one RFC that was loosely adopted
by the browser authors.  :)

> The SSL server that I am transfering to is a bank server (outside of my
> control). By default they would prefer to accept the transfer via HTTPS
> and their CGI script. I was hoping for a way to script a POST operation to
> get the file there.

It's possible.

> I'm going to have to jump through some hoops to get the Secure FTP or SSH
> to work for me on their end. I'd rather avoid this if I can find a simple
> way to POST the file via HTTPS.

Understood.

> I tried WGET and realized that they call it GET for a reason. If there is
> such a thing as WPUT that will run secure on SCO that might solve my
> problem.

WPUT is ftp-only, as I've noted somewhere else in this thread.  I have it,
it's a quirky little beta PoS.  It's okay, but it's more limited in putting
than wget is in getting.

> The RawQuery seems to be a possibility but the specifics of how it's going
> to work seem vague. I'll have to look into this.

Assuming we have concurrent uploads at once, I'll use $$ to make each
unique.

Query file: upquery.$$
upload_fieldname=/path/to/file
[whatever other fields are necessary]

rawquery -M -q upquery.$$ -o upresult.$$ -F upload_fieldname \
     -u https://wherever/someupload.cgi 

That takes the field information from the query file, puts any resultant
page in the result file, and makes sure it treats the field
upload_fieldname as a file to upload, rather than as text contents of a
field.  And it makes sure it uses multipart/form-data (the -M) rather than
x-www-form-urlencoded for the encoding scheme.

It's really that simple.  You do have to get Crypt::SSLeay installed
in perl on your machine to use SSL.  If you have SCO 5.0.6, you should
make the necessary updates to get perl 5.8.1 from them, really.  The
earlier versions are much dodgier about XS modules.  Trust me on this. :-/
I've butted heads for hours on things like that, and the 5.8.1 makes it
painless--in fact, I think Crypt::SSLeay comes with their 5.8.1.  If not,
it compiles fine with gcc, as I'm using it on someone's 5.0.6 system.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html


More information about the Filepro-list mailing list