- Issue created by @vaish
Automatically closed - issue fixed for 2 weeks with no activity.
In the past, when crawler/bot rate limiting was the only module feature, it made sense to disable rate limiter if bot limiting is not configured properly (e.g. due to a typo). Now that module provides several additional features, this behavior is not optimal because error in bot limiting configuration ends up disabling rate limiting of regular traffic and all other features.
bot_traffic. Set either "interval" or "requests" to an invalid value (e.g. negative integer)regular_traffic. Set both "interval" and "requests" to valid values.Current behavior: Both bot rate limiting and regular traffic rate limiting are disabled.
Expected behavior: Bot rate limiting is disabled while rate limiting of regular traffic works fine.
Handle each type of rate limiting independently.
N/A
N/A
N/A
Active
3.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.