Re: LW as a web app

> On 11 Feb 2026, at 08:23, Adam Weaver (as adam at cleversure dot com dot au) <[email protected]> wrote:
> 
> Does anyone else use LW for web middleware?
> 
> I'm currently using a DELIVERed LW app to run a web service. Originally I
> wrote a HTTP/1.1 server, but then realised that I didn't want to learn
> HTTP/2 or HTTP/3. So I transitioned the front end to Caddy, and
> reverse-proxied back to my lisp code.

I am not 100% what you are trying to achieve but the way one uses runtimes in the context of webdevelopment is by reverse proxying the request from the outside world via nginx (or any other specialised web server) to the custom language runtime via sockets and optionally an application level web server that interprets the incoming request headers and produces the response, which nginx relays back. This way you isolate your application from things like handling security, encryption and avoiding exposing the commonly incomplete http request handler within your app. 

So you are essentially running two webservers:
1. The reverse proxy (nginx very commonly).
2. The application’s own request handler (or another webserver, like hunchentoot). You seem to have the first option.
3. The reverse proxy simply relays the http requests from the Internet, dealing with the encryption, serving static files, etc. to your own http request handler (or hunchentoot), then sends the response back.

Fast cgi is not needed here, it is an ancient technology from the time when people weren’t quite sure how web development should work and the approach described above is the standard practice nowadays.