X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=TODO;h=1a80902e7751c79b08eedf4b5d01a82234fad9ca;hb=407e94ec9b8779d6b1e6a67eb2aa295ae040cd0c;hp=49ec37414d4aa18b6333cd2fa715c60380559684;hpb=82b3d401f1a12a69483a257c6246641918bd5118;p=privoxy.git

diff --git a/TODO b/TODO
index 49ec3741..1a80902e 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.79 2013/03/01 17:39:46 fabiankeil Exp $
+$Id: TODO,v 1.86 2013/10/30 14:31:23 fabiankeil Exp $
 
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
@@ -122,7 +122,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 
 54) Move away from CVS to a more modern revision control system.
     Find out if there are any objection against going with Git.
-    Using Git would also have the advantage that SF now pretents
+    Using Git would also have the advantage that SF now pretends
     to support it, so we could do it independently from 53).
 
 55) Apply for Coverity scans: http://scan.coverity.com/
@@ -255,7 +255,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
     for misconfigured setups.
 
 95) Support a non-standard client header in CONNECT requests that
-    contains the URL of the requested ressource, which is then treated
+    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
@@ -276,7 +276,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 
 99) Figure out a mechanism through which a user can easily enable
     site-specific action sections that are too aggressive to be
-    enalbled by default. This could be similiar to the presettings
+    enabled by default. This could be similar to the presettings
     in default.action, but could also be just another action file
     that isn't used by default.
 
@@ -287,7 +287,7 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 102) Add an include directive to split the config file into several parts.
 
 103) Potential performance improvement for large action files:
-     when figuring out which actions apply, check the action bitmask
+     when figuring out which actions apply, check the action bit mask
      before pattern matching and skip section that wouldn't modify the
      actions already set. To increase the impact the sections would have
      to be applied in reverse.
@@ -305,15 +305,27 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
 107) Support more pcrs variables, for example $destination-ip-address
      and $source-ip-address.
 
-108) Allow to use a somewhat random string intead of PRIVOXY-FORCE.
+108) Allow to use a somewhat random string instead of PRIVOXY-FORCE.
 
 109) Let log_error() support the format specifier %S which should
      work like %s but escape new lines like %N. This would be useful
      to log the result of header filters which may inject new lines.
 
 110) Add a global-buffer-limit directive that roughly limits how
-     much malloc'ed memory Privoxy will use and can potentionally
+     much malloc'ed memory Privoxy will use and can potentially
      be smaller than (buffer-limit * max-client-connections).
 
 111) Reject requests if hosts and ports in request line and Host
      header don't match (before filters have been applied).
+
+112) If a header filter is used to inject another header by inserting
+     a \r\n (undocumented feature), detect it and split the headers so
+     following header actions do not treat them as a single string.
+     Alternatively add another header injection mechanism.
+
+113) Log statistics upon receiving a certain signal (SIGINFO or SIGUSR1).
+
+114) Properly deal with status code 100. The current "Continue hack"
+     can cause problems for gpg when uploading keys through Privoxy.
+
+115) Add ICAP (RFC 3507) support. FR #3615158.