Hi Stephen,
Thanks for the tip. I was aware that LiveCode does not do SFTP. I had to get
my Mac to start running regular FTP to work with it. I am using a separate
account.
Regards,
Gregory
On Wed, Dec 7, 2011, at 8:50 AM, use-livecode-requ...@lists.runrev.com wrote:
> You should know th
Just a method to get the uploads (and exposed password/user) to a place
that isn't your public website. Most web providers will allow unlimited or
many FTP accounts, and you can use completely different user/passwords.
Some providers (not On-Rev) will allow an account to have multiple users
that
Actually, Stephen, could you elaborate on the "special ftp space" that is not
the website. I'm a little unclear on the distinction.
Mark
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Confirming-an-FTP-Upload-tp4164699p4165858.html
Sent from the Revolution - Us
Stephen,
That's true, and I probably should have mentioned that. For my purposes,
it's irrelevant, because my research data (indeed the entire "site") is all
just a bunch of meaningless numbers that nobody would have any interest in.
But for the rest of you out in the real world, caveat emptor.
Hi Mark,
Much appreciated! Just the kind of thing I was looking for.
Regards,
Gregory
On Tue, Dec 6, 2011, at 1:00 PM, use-livecode-requ...@lists.runrev.com wrote:
> Greg,
> Here's how I submit data using the Put URL approach...
___
use-livecode
You should know that the password and username are sent as plain text and
can be easily sniffed. This is NOT secure FTP and can expose an entire
account. Create a special FTP space for this purpose, not your website.
Secure FTP is a long-awaited feature that is still not available in
livecode ex
Greg,
Here's how I submit data using the Put URL approach...
*put *DataToBeSaved into URL
("ftp://username:passw...@ftp.sitename.com/filename.txt";)
*If* the result is not empty *then*
hide field "wait"
answer the result &CR& "Oops! There was a problem saving your
response. P
