-$Id: TODO,v 1.65 2012/07/23 12:49:51 fabiankeil Exp $
+$Id: TODO,v 1.71 2013/01/05 18:37:35 fabiankeil Exp $
Some Privoxy-related tasks, sorted by the time they
have been added, not by priority.
11) CGI templates should use semantically-correct HTML
and scale properly.
-12) Improve pipelining support.
+12) Support pipelining for outgoing connections.
14) Allow to filter POST parameters.
trivial, though.
88) Investigate if there's a Perl module that Privoxy-Regression-Test
- could optionally use to keep connections alive.
+ could optionally use to keep connections alive, preferably while
+ requiring less forks at the same time.
89) When multiple block actions apply, consider showing all the block
reasons on the blocked page that haven't been overruled, not just
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.
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.
-
102) Add an include directive to split the config file into several parts.
103) Potential performance improvement for large action files:
106) actionlist.h should be embedded in a way that causes less text
segment bloat.
+
+107) Support more pcrs variables, for example $destination-ip-address
+ and $source-ip-address.
+
+108) Allow to use a somewhat random string intead of PRIVOXY-FORCE.