4 ms·
AllegroServe, a web server written in Common Lisp
- remexre 4y ago> We've recently added these features: > [...] > - Security up through TLS 1.0 (SSL 3.1). uhhhhhhhh, isn't this removed from Firefox for having security holes fixed in later versions of the TLS spec?
- fiddlerwoaroof 4y agoThat line is about twelve years old, per git blame. Typically, I’d use a reverse proxy to handle HTTPS anyways.
- nerdponx 4y agoI would almost prefer a web framework that doesn't even bother trying to handle things like HTTPS and assumes that I'm using a reverse proxy in front of it. Fewer things to maintain.
- lf-non 4y agoIs this generally true for compiled languages ? I like being able to handle https in a single go binary for small projects that otherwise don't need a load balancer etc.
- fiddlerwoaroof 4y agoI don't trust random web frameworks to implement HTTPS correctly and there are lots of subtle attacks on cryptography.
- guenthert 4y agoHow does it compare (feature-wise, performance, stability) with e.g. hunchentoot (which clearly wins the naming contest)?
- jinwoo68 4y agoI think this runs only with Allegro Common Lisp, a commercial implementation.
- agambrahma 4y agoNot really, you can run this under SBCL too.
- guenthert 4y agoI need another hint. The sources seem to depend on Allegro specifics, e.g. the :excl package (with the enlightening description "General extensions to Common Lisp").
- mikelevins 4y agoYou can load :aserve from qucklisp to get a portable fork of AllegroServe that works with sbcl (or at least it appears to at first glance on my copy of SBCL 2.2.6). The README distributed with the library offers a little guidance to getting started.
- sanxiyn 4y agoYes, AllegroServe is Allegro specific, but there is Portable AllegroServe: http://portableaserve.sourceforge.net/ http://portableaserve.sourceforge.net/ It's the same situation as OpenSSH. OpenSSH only runs on OpenBSD, and Portable OpenSSH is maintained separately.