On 11/28/06, Charlie Coleman <[EMAIL PROTECTED]> wrote: > We've run into some of the things you mentioned above. Some are addressed > by letting the users set some of the FTP options. We are also planning to > add optional HTTP file transfer pretty soon. Mainly to be able to have > 'secure' transmission (HTTPS) - but to date the data was considered public > anyway so this hasn't been a priority. We do send files in both directions, > so figuring out the right use of HTTP "post?" to send a file is still in > the works.
Have you consider SCP - Secure Copy? It's a copy command over SSH, a far more secure and reliable way of doing things than trying to transfer files via Hypertext Transfer Protocol. I use SCP and SSH (or rsync-over-ssh) to execute remote scripts and doing backup copies on several platforms. O'Reilly's "snail book" does a good job of covering commercial and non-commercial solutions. Re: network knowledge: few employers pay for the training needed, and few "techs" get the amount of training they need on basic things like network hardware and protocols. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
