WebMask beta release
--------------------

Note that this is a beta release, and as such not all of the options, bugs,
and limitations may yet be quite as obvious as they should be.  Some of
them are listed below.  Please report anything else you discover that
you think should be fixed, or documented somewhere, or that you think could
be improved.  See also the wishlist (in wishlist.txt).

Hidden amongst the debug options are some settings to allow the main window
to be displayed, in various styles.  This can be useful, even when not
debugging WebMask.  Unlike the other options on these pages, they're
suitable for normal use and (hopefully) aren't going to cause odd things
to happen if used indiscriminately.  The settings in question are 8, 2000,
4000, 8000, and 10000 on the 'Debug 1' tab.

By default, the currently-active filters are saved in _webmask.wff in the
same directory as webmask.exe is running from.  It's loaded on startup, and
is saved whenever any changes to the 'Filters' tab are applied.  The
'Save...' button will save a copy to another file, but won't affect which
file is automatically loaded on startup.  Editing _webmask.wff while
WebMask is running is a bad idea as it won't have an immediate effect, and
it will be overwritten (without warning) if you then alter any filters from
the properties dialog box.  In fact, it's probably not a good idea, in most
cases, to edit any .wff by hand, as it was only intended to be human-
readable and not human-writable.  While it is possible, WebMask is very
exacting with the format used, and extra blank lines, for example, may
confuse it.

This use of _webmask.wff is also able to cause another problem.  The file
is stored in the same directory as webmask.exe.  Normally, this is
perfectly acceptable.  However if two people run WebMask from the same
directory, they'll end up using the same filters file.  As it's only read
on startup, if both users make a change, then the first set of changes
will be lost.  One solution is clearly not to run WebMask from a network
path, and this is the preferred solution.  However it is possible to make
WebMask look elsewhere for its file.  To do this, exit WebMask, then edit
registry key HKCU\Software\PseudoFoo\WebMask\filterFile to point to some
other filename.  A relative path is relative to the directory containing
webmask.exe.  An absolute path is also allowed.  As a last resort, if it
is set to an empty string, WebMask will save its filters directly in the
registry.  This is very slow, and is not recommended.

The 'Via' text that WebMask adds to the HTTP header is currently added to
the end of every header line found starting with "Via:".  This is incorrect
if more than one such line is present.  In practice, WebMask will normally
be the first (or only) proxy in the chain, and so there won't be an
existing 'Via' header to alter (and a new one will be added).

WebMask doesn't detect recursive calls to itself.  It's not a good idea to
set the proxy chain up like this.

Email: webmask@flourish.org