Silverstripe CMS comes with a Middleware that provides rate limiting for the Security controller. This provides added protection to a potentially vulnerable part of a Silverstripe CMS application where an attacker is free to bombard your login forms or other Security endpoints.
Applying rate limiting to controllers
You can apply rate limiting to other specific controllers or your entire Silverstripe CMS application. When applying rate limiting to other controllers you can define custom limits for each controller.
First, you need to define your rate limit middleware with the required settings:
ExtraKey: 'mylimiter' # this isolates your rate limiter from others
MaxAttempts: 10 # how many attempts are allowed in a decay period
Decay: 1 # how long the decay period is in minutes
Next, you need to define your request handler which will apply the middleware to the controller:
RequestHandler: '%$MyController' # the fully qualified class name of your controller
- '%$MyRateLimitMiddleware' # the rate limiter we just defined in the last step
Finally, you need to define the custom routing:
Or if you want to apply your middleware to a specific route:
Applying rate limiting across an entire application
If you'd like to add rate limiting to an entire application (ie: across all routes) then you'll need to define your rate limit middleware much like the first step outlined in the previous section and then you'll have to apply it to the entire site as you would with any other middleware:
Disabling the rate limiter
You may already solve the rate limiting problem on a server level and the built in rate limiting may well be redundant. If this is the case you can turn off the rate limiting middleware by redefining the URL rules for the Security controller.
Add the following to your config.yml: