1 $Id: TODO,v 1.32 2011/01/24 18:12:44 fabiankeil Exp $
3 Some Privoxy related tasks, 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 deflate content before sending it to
45 the client. Measure if it makes a difference.
48 Note that this is already being worked on and mostly done
49 for buffered content and internal CGI responses.
51 The difference it does make, seems to be that it slows things
52 down if the client and Privoxy are running on the same system,
53 so for most users enabling it will make no sense.
55 14) Log and filter POST parameters. They can now be logged with
56 the noisy debug 32768, but are still not filtered.
58 15) If trusted CGI pages are requested without trusted referrer,
59 set the status code to 403 instead of 200.
61 16) Filter SSL encrypted content as well.
63 At the beginning we could use a unencrypted connection between
64 client and Privoxy, and use an encrypted connection between
65 Privoxy and the server.
67 This should be good enough for most of the content the
68 user would want to filter.
70 19) enable-forward-fallback. Syntax? Suggested by K.R.
72 21) User Manual delivery doesn't accept multiple slashes. Should it?
74 22) Verify action files properly (Including arguments) and
75 act accordingly (should probably intercept all requests
76 with a "Invalid option foo detected" CGI page).
78 23) Do the same in case of syntax errors in the configuration file,
79 instead of just exiting or ignoring the problem.
81 25) Handle multiple filters with the same name better. Reject them?
83 26) Let show-url-info detect clearly invalid URLs.
85 27) Make errno logging less thread-unsafe.
86 Verify that it's really an improvement.
88 28) Don't take default ports in case of invalid forwarding ports.
90 31) If a string action foo is disabled csp->action->string[ACTION_STRING_FOO]
91 doesn't necessarily contain NULL, but may contain the string of an
92 enabled foo action in an overruled section. Is it a bug? Does it matter?
94 32) In case of forwarding failures with socks port == 9050,
95 show extra info about Tor (the whole FAQ entry?).
97 35) Do less work in the accept_connection() thread.
98 Partly done. Good enough?
100 36) Unload unused action files directly, even if they are
101 disabled without replacement.
103 38) In the final results, explicitly list disabled multi actions
104 with their parameters. Not as trivial as it sounds.
106 39) Verify loadcfg.c jarfile reloading and friends.
107 /* XXX: Does disabling this actually work? */
109 40) Fix core dumping in daemon mode. Introduce a cwd config option?
111 41) Change documentation framework to one that works cross-platform.
114 42) Add DTrace hooks. Now that FreeBSD has userland DTrace
115 support there's no longer any reason not to.
117 43) Write a tool to check URL patterns against URLs in the log file.
118 This could be included in Privoxy-Regression-Test.
120 44) Privoxy-Log-Parser: Consider highlighting "Connection" in:
121 23:13:03.506 283b6100 Header: Replaced: 'Connection: Keep-Alive' with 'Connection: close'
123 49) Add FAQ for NTLM proxies. Still necessary?
125 50) Investigate possible PCRS template speedup when searching
126 macros with strstr() before compiling pcrs commands.
127 Investigated, needs some restructuring but is probably worth it.
129 51) Make user-manual directive more generic to allow serving
130 the FAQ and other stuff, too. Consider changing the port
131 for "same origin policy" issues.
133 53) Find a more reliable hoster. Involves finding out what our
134 requirements are and which SF alternatives fulfil them.
135 It would probably also make sense to look into what other
136 projects did when migrating away from SF.
138 54) Move away from CVS to a more modern revision control system.
139 Find out if there are any objection against going with Git.
140 Using Git would also have the advantage that SF now pretents
141 to support it, so we could do it independently from 53).
143 55) Apply for Coverity scans: http://scan.coverity.com/
145 56) Apply for the "free online access for qualified open-source
146 software projects" for the Co-Advisor HTTP compliance tests:
147 http://coad.measurement-factory.com/details.html#pricing
149 57) Allow piping into external programs to allow more powerful
150 filters and policy decisions. Incomplete support available
151 in Fabian's popen branch.
153 58) Move more template strings from the code into the actual templates.
155 59) Import the German template translation.
157 60) Ask the Russian translators for input on how to make their
160 61) Consider (optionally?) skipping the hostname comparison when
161 checking if a connections that goes to a HTTP proxy can be reused.
162 Do all HTTP proxy support that? Is it worth it?
164 63) Reject clearly too large requests earlier?
166 64) Use proper copyright attribution. "Privoxy Developers"
169 65) Polish Website. Probably involves ditching the Docbook
170 mess in favour of wml. There should be already some threads
171 in the mailinglists archives about this.
173 66) Increase maximum number of action and filter files.
175 67) Clean up directory layout. Depends on 54 so we don't
176 lose the revision history.
178 68) Use standard make syntax so we don't depend on GNU make.
180 69) Update autoconf setup (or move away from it).
182 70) If the server connection is reset but the headers are
183 received, consider passing the mess to the client instead
184 of showing the connect-failed template. Relates to #2698674.
186 71) Allow to listen on multiple addresses without having to
189 74) Let Privoxy-Regression-Test optionally check that action
190 sections which disable actions actually are preceded by
191 sections that enable said actions.
193 75) Create a tool that creates Privoxy action (and filter?) files
194 out of adblock files. Could be implemented as option for
195 url-pattern-translator.pl.
197 76) Cache DNS responses. Note that this has been requested
198 several times by users, but is not a developer priority.
199 If you care about this, feel free to submit patches.
201 77) Allow to configure the IP address used in outgoing connections.
203 78) Allow to optionally use pcre's DFA algorithm.
205 79) Evaluate pcre alternatives.
207 80) Change FEATURE_EXTENDED_HOST_PATTERNS to support both
208 extended and vanilla host patterns at the same time.
210 Note that the requirement is to allow the user to decide
211 if the domain pattern should be interpreted as regex or
212 traditional host pattern and if it's not obvious that the
213 user made any decision, default to the latter.
215 Possible solutions would be:
217 1. An always-use-regex-domain-patterns config option
218 2. An enable-regex-domain-patterns-for-this-action-file option
219 3. An enable-regex-domain-patterns-for-this-action-file-until-the-user-says-otherwise option
220 4. A treat-the-domain-pattern-in-this-line-as-regex(-or-not) option
221 5. Combinations of the options above
223 With 2+4, 3+4 or 2+3+4 being the preferences until
226 81) Merge Fabian's unlimited-config-lines branch.
228 82) Detect if the system time goes back in time let the user
229 know if it caused any connections to get closed.
231 83) Make the FAQ available through the CGI interface like the
234 84) Flesh out the user-manual delivery to serve pages from
235 other directories, too.
237 85) Once #84 is done, write a script that populates a directory with
238 various common third-party icons (stumbleupon.png, facebook.png ...)
239 and redirect requests for them to Privoxy.
241 86) Add a server-body-tagger action. This is trivial as as all the
242 functionallity required to do it already exists.
244 87) Add a client-body-tagger action. This is less trivial as we currently
245 don't buffer client bodies. After 14) is implemented it would be
248 88) Investigate if there's a Perl module that Privoxy-Regression-Test
249 could optionally use to keep connections alive.
251 89) When multiple block actions apply, consider showing all the block
252 reasons on the blocked page that haven't been overruled, not just