Install

Works with Drupal: ^8.8 || ^9

Using dev releases is not recommended, except for testing.

Using Composer to manage Drupal site dependencies

Alternative installation files

Download httpbl-8.x-1.x-dev.tar.gztar.gz 67.79 KB
MD5: 04fbeb94be4b6cc1e53c4019c73d0493
SHA-1: 350435eb26397cdacd98ff6f0019e973fa9e0e73
SHA-256: c6211a1ec435e320404b3a0f3e09b2a89a093d51263e9e44939b99fca8bc457f
Download httpbl-8.x-1.x-dev.zipzip 112.29 KB
MD5: 3fd05c4d017286fe696a6198ba0c904c
SHA-1: aa53e615b08226473d2f05f6bd4246ecac93eee3
SHA-256: 07dd0cdb8495d62f47f9ec9da2b0939571d97aab8364878fa762db61576f0abb

Release notes

Development release for Drupal 8.x (It's Alive!)

This initial development release for httpbl (D8) represents a major upgrade and re-write. It was started with a clean slate, however it maintains all the primary functionality that the module has provided since the original D5 version—namely, checking IP addresses during page requests OR comment submissions, against Project Honeypot (.org), and determining whether or not to locally blacklist, grey-list or white-list those IPs based on any found threat scores (or the absence of any scores).

What's new in D8 is that records are now stored as manageable "Host" entities, with a brand new Admin View UI that includes bulk actions, for managing them. You still don't have to manage them, but now, for the first time, you can—without needing any direct access to your database. Httpbl still does what it does best, working quietly in the background to minimize nuisance traffic, but whether you're a control freak or just like seeing how many IPs your site has captured, you now can.

Prudence requires advising this development release not be used in a mission critical production environment, but it is a stable release. There are not yet any automated tests, nor is there any migration path for moving previous installation data from D6 or D7.

For the sake of future planning, it also must be advised that this project will soon, again, be forked, and move in a slightly different direction than it has since at least D6, namely, how it will work with any page-request blocking in Drupal core. In past releases, Httpbl shared its blacklist with whatever table Drupal core was using for banning traffic (the names and methods have been different for D6 and D7), and now in D8 Httpbl still does this cooperatively with the new Ban module. This is going to go away in future releases. The reason is that Drupal banning in the past was not optional, but now it is; you don't have to enable the Ban module. Httpbl proposes that as long as that is true, there is no need to have both Ban and Httpbl running, as both are middleware services doing essentially the same thing with the same, shared list.

But for the time being, we wanted to be able to honestly state that Httpbl does everything it used to do, and more!

The 8.x codebase is also available on Github. There is also a Wiki there that explains more about the current state of this project, and why this module's support for the Ban module will be dropped in the future.

Created by: bryrock
Created on: 24 Mar 2017 at 23:03 UTC
Last updated: 15 Jul 2022 at 21:41 UTC
New features

Other releases