+
+86) Add a server-body-tagger action. This is trivial as as all the
+ functionallity required to do it already exists.
+
+87) Add a client-body-tagger action. This is less trivial as we currently
+ don't buffer client bodies. After 14) is implemented it would be
+ trivial, though.
+
+88) Investigate if there's a Perl module that Privoxy-Regression-Test
+ could optionally use to keep connections alive.
+
+89) When multiple block actions apply, consider showing all the block
+ reasons on the blocked page that haven't been overruled, not just
+ the last one.