mholt/caddy-ratelimit

Different storage for rate_limit

odarriba opened this issue · 1 comments

Hello,

Is it possible to store rate_limit related information in a different storage than the default Caddy's one?

If you for example use NFS to synchronize TLS certificates and so on, it would be nice to be able to set another storage (like Redis?) for rate_limit, as the delay in NFS reads/writes can affect the performance of the rate limiter.

Thanks in advance

Is it possible to store rate_limit related information in a different storage than the default Caddy's one?

Yes. See in the JSON config, the handler configuration can take storage as one of the parameters.

The same thing for the Caddyfile config.