Change two block reasons that previsouly were the same

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index 97492a9..4dfebb5 100644 (file)
--- a/TODO
+++ b/TODO
@@ -179,25 +179,6 @@ https://www.privoxy.org/faq/general.html#DONATE
 
 79) Evaluate pcre alternatives.
 
 
 79) Evaluate pcre alternatives.
 

-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.
-

 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 
 82) Detect if the system time goes back in time let the user
     know if it caused any connections to get closed.
 


@@ -442,6 +423,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)