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 "stunnel4") ) --- # stunnel.conf --- debug = 4 output = /home/alex/stunnel.log pid = /home/alex/stunnel.pid cert = /home/alex/https-server.pem CApath = /etc/ssl/certs sslVersion = all options = NO_SSLv2 options = NO_SSLv3 [https] accept = 8443 connect = 8080 --- AW *https://aw.github.io/picolisp <https://aw.github.io/picolisp>* On Tue, May 26, 2015 at 11:25 PM, Luis P. Mendes <[email protected]> wrote: > 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 question, can a https server application be build in Picolisp > with a certificate signed by some CA? > If so, what part of the documentation am I missing? > > Luis > -- > UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe >
