It appears that you can only set the timeWindow option once globally, when registering the hapi-brute plugin, thanks to the way how it is used to construct the TTL for the cache the plugin creates.
All other options can be set on a per-route basis when defining once routes, but the timeWindow not. Well it can be set, but it will not have any effect.
It is because there is a single cache which is configured on server registration. I guess it is possible to instantiate another with a different expiry if the route requires it.
It appears that you can only set the timeWindow option once globally, when registering the hapi-brute plugin, thanks to the way how it is used to construct the TTL for the cache the plugin creates.
All other options can be set on a per-route basis when defining once routes, but the timeWindow not. Well it can be set, but it will not have any effect.