3 ms·
I look through my server logs sometimes and often see connection and request throttling being activated, by those who are hitting the servers with their automat
by heurisko 4y ago
I look through my server logs sometimes and often see connection and request throttling being activated, by those who are hitting the servers with their automated exploit tools. I see having some sort of throttling as essential as being able to set the max client body file size to prevent abuse.
Of course, I could run something else in front of the server, but it's simpler for my use cases not to. The auto-SSL and simplified configuration were very attractive things about Caddy, however.
If your CMS provides it, maybe you could run an exit poll for people who demo Caddy, then look elsewhere, as I'm just speaking from my own experience.
- francislavoie 4y agoUnderstood, I'm not saying it's not generally useful, I'm specifically talking about this implementation; is the way it was built useful, does it actually solve user's rate limiting needs? We need people to try to the plugin so we can mould it to user's needs. Then later we can bundle it once we're sure it's designed properly and we're locked-in on the approach taken.
- heurisko 4y agoIndeed, I see where you are coming from. However I wonder if it would work better if the module were brought under the Caddy namespace and marked "beta". At least then, there would be a show of commitment for the idea, if not the implementation. Recently I've been looking at the Symfony framework, and this is how they introduce features, with a clear warning that the API etc. is subject to change.