1 $Id: TODO,v 1.20 2010/09/14 07:12:20 fabiankeil Exp $
3 Some Privoxy related task, not ordered in any way.
5 1) Add some regression tests. Filters should be tested automatically
6 (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
8 3) Fix some more XXX: comments.
10 4) Fix some more compiler warnings. (Especially on amd64)
13 6) Remove actions that aren't needed anymore:
15 content-type-overwrite should probably stay as it's also
16 used by some of the CGI pages (XXX: name them).
18 crunch-client-header and crunch-server-header should probably
19 go, their only advantage is that their search strings can be
20 controlled through the CGI pages, other than that they only
23 crunch-if-none-match can be replaced with a header filter.
25 prevent-compression has a misleading name and could
26 be replaced with a header filter.
28 7) force-text-mode has a stupid name and should probably
29 be renamed to force-filter-mode.
31 8) handle-as-empty-document and handle-as-image should
32 be merged to something like handle-as{something} to
33 prevent them from being activated at the same time.
35 10) There's a bug in the CGI editor that turns the
36 first section's "Insert new section below" into
37 a "Insert new section above" button.
39 11) CGI templates should use semantically-correct HTML
42 12) Add pipelining support.
44 13) Use zlib to compress content before sending it to
45 the client. Measure if it makes a difference.
47 14) Log and filter POST parameters. They can now be logged with
48 the noisy debug 32768, but are still not filtered.
50 15) If trusted CGI pages are requested without trusted referrer,
51 set the status code to 403 instead of 200.
53 16) Filter SSL encrypted content as well.
55 At the beginning we could use a unencrypted connection between
56 client and Privoxy, and use an encrypted connection between
57 Privoxy and the server.
59 This should be good enough for most of the content the
60 user would want to filter.
62 19) enable-forward-fallback. Syntax? Suggested by K.R.
64 21) User Manual delivery doesn't accept multiple slashes. Should it?
66 22) Verify action files properly (Including arguments) and
67 act accordingly (should probably intercept all requests
68 with a "Invalid option foo detected" CGI page).
70 23) Do the same in case of syntax errors in the configuration file,
71 instead of just exiting or ignoring the problem.
73 25) Handle multiple filters with the same name better. Reject them?
75 26) Let show-url-info detect clearly invalid URLs.
77 27) Make errno logging less thread-unsafe.
78 Verify that it's really an improvement.
80 28) Don't take default ports in case of invalid forwarding ports.
82 31) If a string action foo is disabled csp->action->string[ACTION_STRING_FOO]
83 doesn't necessarily contain NULL, but may contain the string of an
84 enabled foo action in an overruled section. Is it a bug? Does it matter?
86 32) In case of forwarding failures with socks port == 9050,
87 show extra info about Tor (the whole FAQ entry?).
89 35) Do less work in the accept_connection() thread.
90 Partly done. Good enough?
92 36) Unload unused action files directly, even if they are
93 disabled without replacement.
95 38) In the final results, explicitly list disabled multi actions
96 with their parameters. Not as trivial as it sounds.
98 39) Verify loadcfg.c jarfile reloading and friends.
99 /* XXX: Does disabling this actually work? */
101 40) Fix core dumping in daemon mode.
103 41) Change documentation framework to one that works cross-platform.
106 42) Add DTrace hooks.
108 43) Write a tool to check URL patterns against URLs in the log file.
109 This could be included in Privoxy-Regression-Test.
111 44) Privoxy-Log-Parser: Consider highlighting "Connection" in:
112 23:13:03.506 283b6100 Header: Replaced: 'Connection: Keep-Alive' with 'Connection: close'
114 49) Add FAQ for NTLM proxies. Still necessary?
116 50) Investigate possible PCRS template speedup when searching
117 macros with strstr() before compiling pcrs commands.
118 Investigated, needs some restructuring but is probably worth it.
120 51) Make user-manual directive more generic to allow serving
121 the FAQ and other stuff, too. Consider changing the port
122 for "same origin policy" issues.
124 53) Find a more reliable hoster. Involves finding out what our
125 requirements are and which SF alternatives fulfil them.
126 It would probably also make sense to look into what other
127 projects did when migrating away from SF.
129 54) Move away from CVS to a more modern revision control system.
130 Find out if there are any objection against going with Git.
131 Using Git would also have the advantage that SF now pretents
132 to support it, so we could do it independently from 53).
134 55) Apply for Coverity scans: http://scan.coverity.com/
136 56) Apply for the "free online access for qualified open-source
137 software projects" for the Co-Advisor HTTP compliance tests:
138 http://coad.measurement-factory.com/details.html#pricing
140 57) Allow piping into external programs to allow more powerful
141 filters and policy decisions.
143 58) Move more template strings from the code into the actual templates.
145 59) Import the German template translation.
147 60) Ask the Russian translators for input on how to make their
150 61) Consider (optionally?) skipping the hostname comparison when
151 checking if a connections that goes to a HTTP proxy can be reused.
152 Do all HTTP proxy support that? Is it worth it?
154 63) Reject clearly too large requests earlier?
156 64) Use proper copyright attribution. "Privoxy Developers"
159 65) Polish Website. Probably involves ditching the Docbook
160 mess in favour of wml. There should be already some threads
161 in the mailinglists archives about this.
163 66) Increase maximum number of action and filter files.
165 67) Clean up directory layout. Depends on 54 so we don't
166 lose the revision history.
168 68) Use standard make syntax so we don't depend on GNU make.
170 69) Update autoconf setup (or move away from it).
172 70) If the server connection is reset but the headers are
173 received, consider passing the mess to the client instead
174 of showing the connect-failed template. Relates to #2698674.
176 71) Allow to listen on multiple addresses without having to
179 74) Let Privoxy-Regression-Test optionally check that action
180 sections which disable actions actually are preceded by
181 sections that enable said actions.
183 75) Create a tool that creates Privoxy action (and filter?) files
184 out of adblock files. Could be implemented as option for
185 url-pattern-translator.pl.
187 76) Cache DNS responses. Note that this has been requested
188 several times by users, but is not a developer priority.
189 If you care about this, feel free to submit patches.
191 77) Allow to configure the IP address used in outgoing connections.
193 78) Allow to optionally use pcre's DFA algorithm.
195 79) Evaluate pcre alternatives.
197 80) Change FEATURE_EXTENDED_HOST_PATTERNS to support both
198 extended and vanilla host patterns at the same time.