X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=0db8372a319354fb363e47adca0f7796ab65d9c1;hp=bfb0bc664bca74937e187b099717bb6bf2e4d497;hb=5d616e2e5dab2e6e3604f0917281ff6ea4eaaad1;hpb=f48fecefb060c8925c055735e14a728b751aa11b

diff --git a/TODO b/TODO
index bfb0bc66..0db8372a 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,7 @@
-$Id: TODO,v 1.29 2010/12/18 12:09:43 fabiankeil Exp $
+$Id: TODO,v 1.33 2011/02/10 22:16:55 fabiankeil Exp $
 
-Some Privoxy related task, not ordered in any way.
+Some Privoxy related tasks, sorted by the time they
+have been added, not by priority.
 
 1)  Add some regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
@@ -41,9 +42,17 @@ Some Privoxy related task, not ordered in any way.
 
 12) Add pipelining support.
 
-13) Use zlib to compress content before sending it to
+13) Use zlib to deflate content before sending it to
     the client. Measure if it makes a difference.
 
+    Update:
+    Note that this is already being worked on and mostly done
+    for buffered content and internal CGI responses.
+
+    The difference it does make, seems to be that it slows things
+    down if the client and Privoxy are running on the same system,
+    so for most users enabling it will make no sense.
+
 14) Log and filter POST parameters. They can now be logged with
     the noisy debug 32768, but are still not filtered.
 
@@ -239,3 +248,7 @@ Some Privoxy related task, not ordered in any way.
 
 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.