X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=TODO;h=b23841bcf237291e243b7ef3a368cb1161ca86ef;hb=dd1f9a5aeefd42d7c935aca826a218a47758fb6a;hp=86cce1f2a1c9a02ba2ecaac4e9b85a0768869d32;hpb=6029432306d7f8c2a80b523f763046d66a3e1383;p=privoxy.git diff --git a/TODO b/TODO index 86cce1f2..b23841bc 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.155 2017/01/23 13:03:26 fabiankeil Exp $ +$Id: TODO,v 1.165 2017/05/29 10:40:28 fabiankeil Exp $ Some Privoxy-related tasks, sorted by the time they have been added, not by priority. @@ -53,9 +53,6 @@ http://www.privoxy.org/faq/general.html#DONATE 14) Allow to filter POST parameters. -15) If trusted CGI pages are requested without trusted referrer, - set the status code to 403 instead of 200. - 16) Filter SSL encrypted content as well. At the beginning we could use a unencrypted connection between @@ -417,7 +414,7 @@ http://www.privoxy.org/faq/general.html#DONATE forward-override). Investigate and fix or document. 141) Port Privoxy to CloudABI, which, despite the name, is actually - rather neet. https://github.com/NuxiNL/cloudlibc + rather neat. https://github.com/NuxiNL/cloudlibc 142) Remove or update the "internal" pcre version. @@ -442,9 +439,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 @@ -456,6 +450,30 @@ http://www.privoxy.org/faq/general.html#DONATE duplicated requests are pointless even if they don't end up with a 404. +153) Catch SIGINT and use it to close the listen socket, serve + remaining connections and shut down. This would allow higher + uptime and make testing more convenient. + +154) Underline links in docs and cgi pages. More precisely, + don't mess with the browser defaults for link underlining. + +155) The sig_handler() shouldn't call log_error(). + While it isn't known to cause actual problems in normal operation, + it's technically incorrect and causes crashes when running in + valgrind. + +156) Reject socks requests with an explicit error message similar + to the one used for ftp. Motivation: + https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html + +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. + In case of lots of idle connections lots of waiting threads are used. + While it's conceivable that this ineffiency is irrelevant from a + performance point of view, using a single thread should reduce Privoxy's + memory footprint a bit which may be noticeable in case of multi-user setups + with hundreds of idle connections. ########################################################################## Hosting wish list (relevant for #53)