wfr747 wrote: ↑
Sun Sep 09, 2018 11:36 am
BTW: how would I write back to the Internet-File?
carefully. After all, if it's easy for you to overwrite files on a server, it would be easy for criminals anywhere in the world to do the same.
HTTPS is usually the best choice for most server tasks, unless you have a specific reason why another protocol is more suited to your needs. For simply writing data to a server, it's the most commonly used.
On the server you will need a program to work in conjunctions with your web server application to handle the specifics of your write request. This common need is handled by the Common Gateway Interface (CGI), and a version of LiveCode, LiveCode Server, is available for use on servers supporting CGI, such as Apache.
See LC's Dictionary for how to use the POST command to send data to an HTTP/HTTPS server, and this tutorial for how to accept that data:
http://lessons.livecode.com/m/4070/l/36 ... ode-server
To avoid misuse of your server by others, you will likely want some form of authentication for write actions. Whether HTTP Basic Auth is sufficient or something more is needed will depend on the sensitivity of the data and what else is on the server. In most cases Basic Auth is fine.
With any sensitive communications you'll want to encrypt the connection so eavesdroppers do not see the password in transit. That's where HTTPS comes in, as opposed to HTTP. Let's Encrypt and other services now provide free web server security certificates to allow HTTPS at no cost. Contact your hosting company to set up a free certificate if you do not already have one in place.
There are other considerations, but this will get you started. I wish I could report that managing a server is as easy as managing client software, but with all servers under constant attack by very smart people using very good tools, we must be diligent lest our server become compromised for use by criminals.