@wezm
httproxide
Memory safe (and not built atop a pile of non-memory safe code E.g. node or Python)
Mostly memory-safe, it’s built on top of Rust + tokio + hyper + rustls, some low-level crypto stuff is always needed since you can’t do constant-time in Rust (in my case I just depend on aws-lc).
Not a kitchen sink: only need HTTP (v 1.x is fine, maybe v2) TLS, static file serving, and reverse proxying
It’s somewhat modular, the base architecture is a Service / Layer concept like popularized by tower, the services / layers all have compile-time switches so you can decide what you want in your version.
Production grade & at least some efforts gone into securing it (sandboxing, efforts to avoid path traversal, things like that)
It’s been serving my stuff for a few years now, I don’t think anyone else uses it. I do try to be aware of basic security best practises, try to re-use components from mature web frameworks (axum), but of course no guarantees. I usually just run it as a systemd service with very few privs, I don’t really think sandboxing inside the webserver makes sense.
Not developed with LLMs
Developed before LLMs were a thing ;)