X-Git-Url: http://www.privoxy.org/gitweb/misc.html?a=blobdiff_plain;f=TODO;h=a490df31c6a95b94ec8a908d832770269fe02f1d;hb=3024a15e4e2641271d5a7f8d28cb49eb436bcde7;hp=95a1be86511db2dd30368d99c590a52f1873c257;hpb=c32ef8dccd73237468f55f0301db83a4d8b539a7;p=privoxy.git
diff --git a/TODO b/TODO
index 95a1be86..a490df31 100644
--- a/TODO
+++ b/TODO
@@ -1,8 +1,11 @@
-$Id: TODO,v 1.40 2011/04/16 17:30:23 fabiankeil Exp $
+$Id: TODO,v 1.59 2011/10/16 17:33:41 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,7 +99,7 @@ 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.
43) Write a tool to check URL patterns against URLs in the log file.
@@ -164,12 +156,12 @@ have been added, not by priority.
65) Polish Website. Probably involves ditching the Docbook
mess in favour of wml. There should be already some threads
- in the mailinglists archives about this.
+ in the mailinglists archives about this. See also #41.
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.
@@ -179,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.
@@ -222,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.
-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.
@@ -254,3 +240,51 @@ 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.
+
+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.