Re: https server side

2015-05-26 Thread Alexander Burger
On Wed, May 27, 2015 at 04:45:27AM +, Alexander Williams wrote: My approach uses stunnel4, which is available on most *NIX systems. It launches an HTTPS listener on port 8443, and forwards to the regular PicoLisp HTTP server on port 8080. The problem with tools like stunnel or nginx is

Re: https server side

2015-05-26 Thread Alexander Williams
Hi Luis, My approach uses stunnel4, which is available on most *NIX systems. It launches an HTTPS listener on port 8443, and forwards to the regular PicoLisp HTTP server on port 8080. # https.l --- (de https-start () (call '/usr/bin/stunnel4 stunnel.conf) ) (de https-stop () (call 'killall

Re: https server side

2015-05-26 Thread Tomas Hlavaty
Hi Luis, PicoLisp comes with httpGate, which is a http and https proxy using openssl library. It is usually run on port 80 and proxies connections to PicoLisp processes. I don't remember the exact command line arguments. I don't use httpGate, but use nginx instead, see

Re: https server side

2015-05-26 Thread Alexander Burger
Hi Luis, that seems to imply that https/SSL has been implemented. So my question, can a https server application be build in Picolisp with a certificate signed by some CA? Yes. PicoLisp application servers may use the 'httpGate' proxy that comes with the distribution. For example, the demo

https server side

2015-05-26 Thread Luis P. Mendes
Hi, I couldn't find anything about the support of https in server side in 'Picolisp by Example' and in 'Picolisp Works' books. But, there's a thread http://t8373.lisp-picolisp-general.lispforum.info/picolisp-ssl-problem-t8373-20.html that seems to imply that https/SSL has been implemented. So my