In case of SOCKS5 failures, do not explicitly log the server's response

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index ce51bf2..b307242 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,8 +1,11 @@
-$Id: TODO,v 1.50 2011/07/19 11:01:14 fabiankeil Exp $
+$Id: TODO,v 1.60 2011/10/16 17:34:26 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.
 
 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.
 
 1)  Add some regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
 


@@ -40,7 +43,7 @@ have been added, not by priority.
 11) CGI templates should use semantically-correct HTML
     and scale properly.
 
 11) CGI templates should use semantically-correct HTML
     and scale properly.
 

-12) Add pipelining support.
+12) Improve pipelining support.

 
 14) Allow to filter POST parameters.
 
 
 14) Allow to filter POST parameters.
 


@@ -208,9 +211,6 @@ have been added, not by priority.
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 

-83) Make the FAQ available through the CGI interface like the
-    user manual is.
-

 84) Flesh out the user-manual delivery to serve pages from
     other directories, too.
 
 84) Flesh out the user-manual delivery to serve pages from
     other directories, too.
 


@@ -265,3 +265,31 @@ have been added, not by priority.
     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.
     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.
+
+99) Figure out a mechanism through which a user can easily enable
+    site-specific action sections that are too aggressive to be
+    enalbled by default. This could be similiar to the presettings
+    in default.action, but could also be just another action file
+    that isn't used by default.
+
+100) Create a cross-platform Privoxy control program and retire
+     the win32 GUI. Integrate support for Privoxy-Regression-Test,
+     Privoxy-Log-Parser, Privoxy-Filter-Test, uagen and similar tools.
+
+101) Forward known client headers in a predefined order that can
+     be changed in the config file. Optionally use a random order.
+     Tools like p0f v3 use the header order for User-Agent detection
+     and thus changing the User-Agent doesn't fool them.