X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=TODO;h=1a2c2a598563ac31f756c579bf0af06877bd70ca;hp=bdd88964b9a0f5c32d04587e59eb4ce0c7b1e341;hb=0ceb8814bb11cbcabdf8908a2cc9b6fae377740c;hpb=d333d842d6b0e1c6af840bca4ecf71bf300ab122 diff --git a/TODO b/TODO index bdd88964..1a2c2a59 100644 --- a/TODO +++ b/TODO @@ -1,14 +1,12 @@ -$Id: TODO,v 1.163 2017/05/20 09:25:14 fabiankeil Exp $ - 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 +https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob_plain;f=TODO;hb=HEAD There's work in progress to fund development on these items using donations. If you want to donate, please have a look at: -http://www.privoxy.org/faq/general.html#DONATE +https://www.privoxy.org/faq/general.html#DONATE 1) Add more regression tests. Filters should be tested automatically (variables too). Could probably reuse large parts of Privoxy-Filter-Test. @@ -53,17 +51,6 @@ http://www.privoxy.org/faq/general.html#DONATE 14) Allow to filter POST parameters. -16) Filter SSL encrypted content as well. - - At the beginning we could use a unencrypted connection between - client and Privoxy, and use an encrypted connection between - Privoxy and the server. - - This should be good enough for most of the content the - user would want to filter. - - Interested donors: 2. - 19) enable-forward-fallback. Syntax? Suggested by K.R. 21) User Manual delivery doesn't accept multiple slashes. Should it? @@ -257,16 +244,6 @@ http://www.privoxy.org/faq/general.html#DONATE 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 resource, 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) Filters should be easier to look up. Currently get_filter() has to go through all filters and skip the filter types the caller isn't interested in. @@ -299,8 +276,6 @@ http://www.privoxy.org/faq/general.html#DONATE files, but only in w32log.c the tray icon is explicitly set. The logging is inconsistent as well. For details see #3525694. -105) Add support for socks authentication. - 106) actionlist.h should be embedded in a way that causes less text segment bloat. @@ -348,7 +323,7 @@ http://www.privoxy.org/faq/general.html#DONATE running out of stack space, causing the kernel to kill Privoxy ungracefully. -121) Add HTTP/2 support. As a first step, incomming HTTP/1.x requests +121) Add HTTP/2 support. As a first step, incoming HTTP/1.x requests should be translated to outgoing HTTP/2 requests where possible (and if desired by the user). Interested donors: 1. @@ -439,9 +414,6 @@ http://www.privoxy.org/faq/general.html#DONATE currently can result in client requests to config.privoxy.org on the Internet which may not be desirable. -149) Use poll() for socket selection so the number of sockets Privoxy - can deal with isn't limited to FD_SETSIZE anymore. - 150) Add blacklistd support. 151) Let the dok-tidy target work cross-platform without introducing @@ -469,8 +441,6 @@ http://www.privoxy.org/faq/general.html#DONATE to the one used for ftp. Motivation: https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html -157) Add a directive to control the currently hardcoded receive-buffer size. - 158) Use a single thread to wait for new requests on reused client connections. Currently the thread that handles the first request on a connection stays responsible for the client connect until it gets closed.