caddy-ratelimit VS cache-handler

You can rate limit HTTP requests (agnostic of specific HTTP versions): https://github.com/mholt/caddy-ratelimit

If you can't already do it with the rate limit module I wrote, open an issue with your detailed requirements: https://github.com/mholt/caddy-ratelimit -- should be pretty straightforward for the most part.

> QoS for a shared-multitenant system, in the presence of customers with really badly tuned and spiky request workloads, whose traffic you must nevertheless mostly accept.

Yah, we see that sometimes. Caddy usually handles it fine, sometimes with a bit of massaging the config.

I'm using caddy for my web server due to it's awesome automatic certificate functionality using Let's Encrypt behind the scenes. Caddy supports rate limiting via this plugin so I don't have to worry about folks killing my API.

That's outdated information. The cache handler plugin is ready to use: https://github.com/caddyserver/cache-handler

In case you missed it: https://github.com/caddyserver/caddy/issues/2786

Those issues are a thing of the past. There's no use bringing it up again, tbh.

> like acting as a cache

That's fair, we have a WIP cache module here https://github.com/caddyserver/cache-handler, it should be ready soon!

All these have been written in the nginx configuration. Caddy is powerful and robust, but I'm not ready to rewrite all these into a Caddyfile. Moreover, a critical feature is missing in Caddy: there isn't a caching layer.