-$Id: TODO,v 1.23 2010/11/06 11:57:31 fabiankeil Exp $
+$Id: TODO,v 1.28 2010/12/14 18:56:11 fabiankeil Exp $
Some Privoxy related task, not ordered in any way.
80) Change FEATURE_EXTENDED_HOST_PATTERNS to support both
extended and vanilla host patterns at the same time.
+
+ Note that the requirement is to allow the user to decide
+ if the domain pattern should be interpreted as regex or
+ traditional host pattern and if it's not obvious that the
+ user made any decision, default to the latter.
+
+ Possible solutions would be:
+
+ 1. An always-use-regex-domain-patterns config option
+ 2. An enable-regex-domain-patterns-for-this-action-file option
+ 3. An enable-regex-domain-patterns-for-this-action-file-until-the-user-says-otherwise option
+ 4. A treat-the-domain-pattern-in-this-line-as-regex(-or-not) option
+ 5. Combinations of the options above
+
+ With 2+4, 3+4 or 2+3+4 being the preferences until
+ further discussion.
+
+81) Merge Fabian's unlimited-config-lines branch.
+
+82) Detect if the system time goes back in time let the user
+ know if it caused any connections to get closed.
+
+83) Make the FAQ available through the CGI interface like the
+ user manual is.
+
+84) Flesh out the user-manual delivery to serve pages from
+ other directories, too.
+
+85) Once #84 is done, write a script that populates a directory with
+ various common third-party icons (stumbleupon.png, facebook.png ...)
+ 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.
+
+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
+ trivial, though.
projects / privoxy.git / blobdiff