Added error checking. Also the payload can now be a string or an array.
command packagePayload @pPayload, pUseEncryption
try
if pPayload is an array then \
put arrayEncode(pPayload) into pPayload
if pUseEncryption then \
put slyEncrypt(pPayload) in
Bob Sneidar wrote:
> I don’t use SSL because I don’t like having to deal with certificates,
> and also because I use a method for encryption that I don’t think
> anyone else has thought of, or at least I can’t find any info online.
Encryption is half of what SSL offers, the other half being exter
Yes, I recently looked at a few reverse proxies. I now run Caddy on
localhost and have some scripts to manage caddyfiles and starting and
stopping the caddy server. Happy to show share if interested in a Zoom.
On Mon, 24 Jun 2024 at 18:56, Mike Kerner via use-livecode <
use-livecode@lists.runrev.
have a look at caddy. it allows you to reverse proxy and have the best of
both worlds:
* server traffic to and from caddy is in the clear, so less mess
* caddy handles all the cert silliness, while also giving you ssl to/from
the clients
we've been doing this for two years (maybe it's three, now).
Hi all.
I came up with deceptively simple wrappers for packaging data for transmission
over raw sockets. I can’t send the slyEncrypt and slyDecrypt handlers because I
use methods no one else knows. But you can roll your own or else eliminate
encryption altogether.
And to answer the question
