I think this runs only with Allegro Common Lisp, a commercial implementation.
I'd also be interested in a feature comparison against Swish (https://github.com/becls/swish), but I'm not actually familiar enough with either to make the comparison myself.
Seems like an unrelated domain; AllegroServe is a web server, Swish looks like a lower-level Erlang-like framework for writing concurrent, fault-tolerant programs. Swish looks very interesting though!
I'd be interested in comparisons with Clack, though, the "other" Common Lisp web framework.
That line is about twelve years old, per git blame. Typically, I’d use a reverse proxy to handle HTTPS anyways.
I 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.
Is 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.