X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=455d21c879d744a5480a2131b7ce3ea73eaa12f8;hb=48855b15032d5740544dcc004887c4cc9c63dee0;hp=0e3dfe0fbe1004b4e183f22c54ab89e487ce8ae9;hpb=9777dbc90b88dd97d12b8bd708bfc697d893d282;p=privoxy.git

diff --git a/TODO b/TODO
index 0e3dfe0f..455d21c8 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,11 @@
-$Id: TODO,v 1.42 2011/04/16 17:31:11 fabiankeil Exp $
+$Id: TODO,v 1.56 2011/09/18 14:41:03 fabiankeil Exp $
 
-Some Privoxy related tasks, sorted by the time they
+Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
 
+The latest version should be available at:
+http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
+
 1)  Add some regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
 
@@ -40,18 +43,7 @@ have been added, not by priority.
 11) CGI templates should use semantically-correct HTML
     and scale properly.
 
-12) Add pipelining support.
-
-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.
+12) Improve pipelining support.
 
 14) Allow to filter POST parameters.
 
@@ -107,9 +99,8 @@ have been added, not by priority.
 41) Change documentation framework to one that works cross-platform.
     Evaluate WML.
 
-42) Add DTrace hooks. Now that FreeBSD has userland DTrace
+42) Add a DTrace USDT provider. Now that FreeBSD has userland DTrace
     support there's no longer any reason not to.
-    DTrace bible preorderd.
 
 43) Write a tool to check URL patterns against URLs in the log file.
     This could be included in Privoxy-Regression-Test.
@@ -169,8 +160,8 @@ have been added, not by priority.
 
 66) Increase maximum number of action and filter files.
 
-67) Clean up directory layout. Depends on 54 so we don't
-    lose the revision history.
+67) Clean up source code directory layout. Depends on 54 so
+    we don't lose the revision history.
 
 68) Use standard make syntax so we don't depend on GNU make.
 
@@ -180,9 +171,6 @@ have been added, not by priority.
     received, consider passing the mess to the client instead
     of showing the connect-failed template. Relates to #2698674.
 
-71) Allow to listen on multiple addresses without having to
-    bind to all.
-
 74) Let Privoxy-Regression-Test optionally check that action
     sections which disable actions actually are preceded by
     sections that enable said actions.
@@ -255,3 +243,41 @@ have been added, not by priority.
     be reasonable to default to a limit of one and showing an error
     message if the request for the redirect URL would be redirected
     again.
+
+92) The statistics currently aren't calculated correctly by Privoxy
+    as each thread is only counted as one request which is no longer
+    correct. This should be fixed, or the statistic code removed.
+    Privoxy-Log-Parser's provides more detailed statistics, anyway.
+
+93) Add a config directive to let Privoxy explicitly request either
+    IPv4 (or IPv6) addresses, even if the system supports both.
+    Could be useful as a workaround for misconfigured setups where the
+    libc returns IPv6 addresses even if there's no IPv6 connectivity.
+
+94) Add a config directive to let Privoxy prefer either IPv4 (or IPv6)
+    addresses, instead of trusting the libc to return them in an order
+    that makes sense. Like #93, this could be useful as a workaround
+    for misconfigured setups.
+
+95) Support a non-standard client header in CONNECT requests that
+    contains the URL of the requested ressource, which is then treated
+    like the request URL.
+
+    This way the client could opt-in for path-based blocking of https
+    requests. Given that the headers from the CONNECT request aren't
+    forwarded to the destination server, an unencrypted URL should be
+    acceptable if the client and Privoxy are running on the same system
+    or in a trusted environment.
+
+96) Enabled filters should be easier to look up. Currently most functions
+    that work with filters spent more (duplicated) code on finding
+    filters than on actually doing something useful with them. Dividing
+    filters by type instead of filter file would reduce the lookup-code
+    quite a bit.
+
+97) Add support for Tor's 'optimistic data' socks extension.
+    Mostly done, not yet pushed to CVS.
+
+98) When showing action section on the CGI pages, properly escape
+    line breaks so they can be copy&pasted into action files without
+    adjustments.