1 $Id: privoxy-to-do-list.txt,v 1.40 2009/05/16 11:25:06 fk 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.
49 15) If trusted CGI pages are requested without trusted referrer,
50 set the status code to 403 instead of 200.
52 16) Filter SSL encrypted content as well.
54 At the beginning we could use a unencrypted connection between
55 client and Privoxy, and use an encrypted connection between
56 Privoxy and the server.
58 This should be good enough for most of the content the
59 user would want to filter.
61 19) enable-forward-fallback. Syntax? Suggested by K.R.
63 21) User Manual delivery doesn't accept multiple slashes. Should it?
65 22) Verify action files properly (Including arguments) and
66 act accordingly (should probably intercept all requests
67 with a "Invalid option foo detected" CGI page).
69 23) Do the same in case of syntax errors in the configuration file,
70 instead of just exiting or ignoring the problem.
72 25) Handle multiple filters with the same name better. Reject them?
74 26) Let show-url-info detect clearly invalid URLs.
76 27) Make errno logging less thread-unsafe.
77 Verify that it's really an improvement.
79 28) Don't take default ports in case of invalid forwarding ports.
81 31) If a string action foo is disabled csp->action->string[ACTION_STRING_FOO]
82 doesn't necessarily contain NULL, but may contain the string of an
83 enabled foo action in an overruled section. Is it a bug? Does it matter?
85 32) In case of forwarding failures with socks port == 9050,
86 show extra info about Tor (the whole FAQ entry?).
88 33) Remove the CVS Log message junk from the C files.
90 35) Do less work in the accept_connection() thread.
91 Partly done. Good enough?
93 36) Unload unused action files directly, even if they are
94 disabled without replacement.
96 38) In the final results, explicitly list disabled multi actions
97 with their parameters. Not as trivial as it sounds.
99 39) Verify loadcfg.c jarfile reloading and friends.
100 /* XXX: Does disabling this actually work? */
102 40) Fix core dumping in daemon mode.
104 41) Change documentation framework to one that works cross-platform.
107 42) Add DTrace hooks.
109 43) Write a tool to check URL patterns against URLs in the log file.
110 This could be included in Privoxy-Regression-Test.
112 44) Privoxy-Log-Parser: Consider highlighting "Connection" in:
113 23:13:03.506 283b6100 Header: Replaced: 'Connection: Keep-Alive' with 'Connection: close'
115 49) Add FAQ for NTLM proxies. Still necessary?
117 50) Investigate possible PCRS template speedup when searching
118 macros with strstr() before compiling pcrs commands.
119 Investigated, needs some restructuring but is probably worth it.
121 51) Make user-manual directive more general to allow serving
122 the FAQ and other stuff, too. Consider changing the port
123 for "same origin policy" issues.
125 53) Find a more reliable hoster.
127 54) Move away from CVS to a more modern revision control system.
129 55) Apply for Coverity scans: http://scan.coverity.com/
131 56) Apply for the "free online access for qualified open-source
132 software projects" for the Co-Advisor HTTP compliance tests:
133 http://coad.measurement-factory.com/details.html#pricing
135 57) Allow piping into external filter programs.
137 58) Move more template strings from the code into the actual templates.
139 59) Import the German template translation.
141 60) Ask the Russian translators for input on how to make their
144 61) Consider (optionally?) skipping the hostname comparison when
145 checking if a connections that goes to a HTTP proxy can be reused.
146 Do all HTTP proxy support that? Is it worth it?
148 63) Reject clearly too large requests earlier?
150 64) Use proper copyright attribution. "Privoxy Developers"
155 66) Increase maximum number of action and filter files.
157 67) Clean up directory layout. Depends on 54 so we don't
158 lose the revision history.
160 68) Use standard make syntax so we don't depend on GNU make.
162 69) Update autoconf setup (or move away from it).
164 70) If the server connection is reset but the headers are
165 received, consider passing the mess to the client instead
166 of showing the connect-failed template. Relates to #2698674.