Page 1 of 1
newLISP web server with SSL
Posted: Wed Jun 16, 2010 7:08 pm
by kanen
Is it possible to run newLISP as a web server and have SSL working? So far, I've only been able to figure out http requests (easy!), but https eludes me.
DragonFly? Crypto? Something else?
Any suggestions, or am I stuck running Apache or Lighttpd or similar to make this happen?
Re: newLISP web server with SSL
Posted: Thu Jun 17, 2010 7:41 am
by itistoday
kanen wrote:Any suggestions, or am I stuck running Apache or Lighttpd or similar to make this happen?
Why do you consider that "stuck"? newLISP's built-in web server isn't exactly designed to serve as a replacement for Apache or lighttpd, it's primarily for testing purposes. Or is this just a matter of convenience?
Re: newLISP web server with SSL
Posted: Thu Jun 17, 2010 3:57 pm
by xytroxon
itistoday wrote:kanen wrote:Any suggestions, or am I stuck running Apache or Lighttpd or similar to make this happen?
Why do you consider that "stuck"? newLISP's built-in web server isn't exactly designed to serve as a replacement for Apache or lighttpd, it's primarily for testing purposes. Or is this just a matter of convenience?
Well... Getting Apache properly configured can be a bit "sticky" ;p)
https requires SSL (encryption) support routines that are not proper for newLISP to include in it's distro...
If you don't mind using closed source software, there is the Abyss Web Server... (Win Mac Linux) This is good light weight server for the non-server-guru (i.e. me ;p)
http://www.aprelium.com/
-- xytroxon
Re: newLISP web server with SSL
Posted: Thu Jun 17, 2010 6:53 pm
by kanen
Perhaps my use of the word "stuck" is more slang in this case.
Either way, my goal was to not have any third-party software installed and do everything from newLISP. If I want SSL, that goal seems like it might not be attainable.
itistoday wrote:kanen wrote:Any suggestions, or am I stuck running Apache or Lighttpd or similar to make this happen?
Why do you consider that "stuck"? newLISP's built-in web server isn't exactly designed to serve as a replacement for Apache or lighttpd, it's primarily for testing purposes. Or is this just a matter of convenience?