-$Id: TODO,v 1.85 2013/08/29 11:21:00 fabiankeil Exp $
+$Id: TODO,v 1.94 2014/02/02 12:03:50 fabiankeil Exp $
Some Privoxy-related tasks, sorted by the time they
have been added, not by priority.
and redirect requests for them to Privoxy.
86) Add a server-body-tagger action. This is trivial as as all the
- functionallity required to do it already exists.
+ functionality required to do it already exists.
87) Add a client-body-tagger action. This is less trivial as we currently
don't buffer client bodies. After 14) is implemented it would be
reasons on the blocked page that haven't been overruled, not just
the last one.
-90) Implement NO-TAG: patterns that enable a section if the
- provided pattern doesn't match any TAG. This would make
- some things cleaner.
-
91) Add an optional limit for internal redirects. It would probably
be reasonable to default to a limit of one and showing an error
message if the request for the redirect URL would be redirected
acceptable if the client and Privoxy are running on the same system
or in a trusted environment.
-96) Enabled filters should be easier to look up. Currently most functions
- that work with filters spent more (duplicated) code on finding
- filters than on actually doing something useful with them. Dividing
- filters by type instead of filter file would reduce the lookup-code
- quite a bit.
+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
line breaks so they can be copy&pasted into action files without
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.
+
+116) Due to the use of sscanf(), Privoxy currently will fail to properly
+ parse chunks whose size can't be represented with 32 bit. This is
+ unlikely to cause problems in the real world, but should eventually
+ be fixed anyway. See also:
+ https://bugzilla.mozilla.org/show_bug.cgi?id=959100
+
+117) Dynamic variables are documented poorly.
+
+118) There should be "escaped" dynamic variables that are guaranteed
+ not to break filters.
+
+119) Evaluate using pcre's jit mode.
+
+120) Add an option to limit pcre's recursion limit below the default.
+ On some platforms the recursion limit doesn't prevent pcre from
+ running out of stack space, causing the kernel to kill Privoxy
+ ungracefully.