Regenerate docs

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index f9c6be7..11b58ca 100644 (file)
--- a/TODO
+++ b/TODO
@@ -51,17 +51,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
 14) Allow to filter POST parameters.
 
 
 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?
 19) enable-forward-fallback. Syntax? Suggested by K.R.
 
 21) User Manual delivery doesn't accept multiple slashes. Should it?


@@ -136,10 +125,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
     Interested donors: 1.
 
 
     Interested donors: 1.
 

-54) Move away from CVS to a more modern revision control system.
-    The move to git is work in progress:
-    https://sourceforge.net/p/ijbswa/mailman/message/34994343/
-

 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.
 58) Move more template strings from the code into the actual templates.
 
 59) Import the German template translation.


@@ -255,21 +240,11 @@ https://www.privoxy.org/faq/general.html#DONATE
     that makes sense. Like #93, this could be useful as a workaround
     for misconfigured setups.
 
     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.
 
 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.
 

-98) When showing action section on the CGI pages, properly escape
+98) When showing action sections on the CGI pages, properly escape

     line breaks so they can be copy&pasted into action files without
     adjustments.
 
     line breaks so they can be copy&pasted into action files without
     adjustments.
 


@@ -351,9 +326,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
 122) Allow customized log messages.
 
 
 122) Allow customized log messages.
 

-123) Evaluate if the voluntarily-disclose-session-keys option in Firefox
-     (and other browsers) can be leveraged. Probably depends on #16.
-

 124) Add support for the "lightweight OS capability and sandbox framework"
      Capsicum. http://www.cl.cam.ac.uk/research/security/capsicum/
      Interested donors: 1.
 124) Add support for the "lightweight OS capability and sandbox framework"
      Capsicum. http://www.cl.cam.ac.uk/research/security/capsicum/
      Interested donors: 1.


@@ -470,6 +442,9 @@ https://www.privoxy.org/faq/general.html#DONATE
      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.
      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.

+
+160) Add keep-alive support with +https-inspection.
+

 ##########################################################################
 
 Hosting wish list (relevant for #53)
 ##########################################################################
 
 Hosting wish list (relevant for #53)