Rebuild after ditching GNUisms in GNUMakefile.in

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 0a2ba92..1b8525e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.44 2011/04/16 17:31:35 fabiankeil Exp $
+$Id: TODO,v 1.52 2011/08/17 10:23:42 fabiankeil Exp $

 
 Some Privoxy related tasks, sorted by the time they
 have been added, not by priority.
 
 Some Privoxy related tasks, sorted by the time they
 have been added, not by priority.


@@ -42,17 +42,6 @@ have been added, not by priority.
 
 12) Add pipelining support.
 
 
 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.
-

 14) Allow to filter POST parameters.
 
 15) If trusted CGI pages are requested without trusted referrer,
 14) Allow to filter POST parameters.
 
 15) If trusted CGI pages are requested without trusted referrer,


@@ -107,9 +96,8 @@ have been added, not by priority.
 41) Change documentation framework to one that works cross-platform.
     Evaluate WML.
 
 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.
     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.
 
 43) Write a tool to check URL patterns against URLs in the log file.
     This could be included in Privoxy-Regression-Test.


@@ -180,9 +168,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.
 
     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.
 74) Let Privoxy-Regression-Test optionally check that action
     sections which disable actions actually are preceded by
     sections that enable said actions.


@@ -260,3 +245,31 @@ have been added, not by priority.
     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.
     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.