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

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 3f0313c..b307242 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.57 2011/10/16 12:40:59 fabiankeil Exp $
+$Id: TODO,v 1.60 2011/10/16 17:34:26 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -211,9 +211,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 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.
 
@@ -287,3 +284,12 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
     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.