Advanced settings for custom expiration dates
bryrock - September 17, 2009 - 21:44
| Project: | http:BL |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | needs review |
Description
Rather than having the expiration offsets for safe, grey-listed and black-listed IPs being written in code, having user selectable expiries in the Advanced settings would make it possible to take more advantage of the httpbl cache {httpbl}.
I'm willing to let white-listed users stick around for 3 days or more before being re-challenged, rather than 3 hours, and as far as I'm concerned, I don't need to see blacklisted traffic back any sooner than 3 years.
I've already implemented this on 4 sites and I'm ready to create a patch for this, but I'll hold off for future snapshots when some of the other issues have reached some resolution.
#1
That would be fine, make the issue active again when you're ready to create a patch.
#2
Great. Thanks. I'll keep you posted.
#3
Here's a patch that adds custom expiration dates for safe/white-listed, greylisted and blacklisted sites.
This lets the user decide how long to they wish to keep already checked IPs in cache {httpbl} to better leverage their cache to avoid repeat dns lookups, especially from some of those more persistent spiders.
These are seen as new settings in the Advanced Settings. Also, any user messages or log entries that refer to these expiries will properly reflect whatever the settings is. For example, "...failed session whitelist request, blacklisted for 26 weeks."
The default settings for white/safe and grey are the same as those previously hard-coded into the module. The blacklist expiry defaults to one year, but can be decreased or increased.