BFilter Documentation
To get BFilter up and running, you usually just install it and configure your
browser to use it. Installing doesn't require any special actions, so it's not
described here. Configuring the browser slightly differs for each kind of them.
The general idea is to set the HTTP proxy setting to localhost:8080, while
preserving the settings for protocols other than HTTP. You only need to do it
when installing BFilter for the first time, not when upgrading.
Here are detailed instructions for Internet Explorer
and Netscape / Mozilla.
Note that you don't want to change these settings before you install BFilter.
Also note that you will need to revert back these changes if you later decide to remove BFilter.
Some users will also need to specify the proxy where BFilter will forward
requests to (most users don't need it).
The Windows installer will try to autodetect it by looking at the Internet Explorer
settings, while still allowing to manually specify it. The only supported proxy
type is unauthenticated HTTP proxy. It should not be a problem to support
other proxy types once someone has requested it.
BFilter also has several configuration files where you can turn on extra features
or configure the filtering behavior for a particular site. These files are located
in $INSTDIR\conf on Windows ($INSTDIR is where you have installed the program to),
or $sysconfdir/bfilter on Unix ($sysconfdir is $prefix/etc unless explicitly set
with ./configure --sysconfdir=, and $prefix is /usr/local unless explicitly set
with ./configure --prefix=).
The general options are located in the file named "config". This file doesn't get
overwrited on upgrade, but instead the new one is stored as "config.default".
The other two files are "rules" and "rules.local". They are used set the
filtering behavior for a particular site or a particular page. They have
exactly the same syntax, and the only difference between them is that
"rules.local" doesn't get overwrited on upgrade. It also has a higher priority.
The configuration options are documented in the files themselves.
Contact the author