Fix a comment typo in header_tagger()

[privoxy.git] / config

diff --git a/config b/config
index 8943ecf..863ff6e 100644 (file)
--- a/config
+++ b/config
@@ -1,6 +1,6 @@
-#        Sample Configuration File for Privoxy v3.0.20
+#        Sample Configuration File for Privoxy 3.0.21
 #
-#  $Id: config,v 1.101 2013/01/09 15:19:47 fabiankeil Exp $
+#  $Id: config,v 1.103 2013/03/02 14:47:05 fabiankeil Exp $
 #
 #  Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
 #
@@ -16,7 +16,8 @@
 #        3. DEBUGGING                                              #
 #        4. ACCESS CONTROL AND SECURITY                            #
 #        5. FORWARDING                                             #
-#        6. WINDOWS GUI OPTIONS                                    #
+#        6. MISCELLANEOUS                                          #
+#        7. WINDOWS GUI OPTIONS                                    #
 #                                                                  #
 ####################################################################
 #
@@ -1103,6 +1104,47 @@ enforce-blocks 0
 #
 buffer-limit 4096
 #
+#  4.9. enable-proxy-authentication-forwarding
+#  ============================================
+#
+#  Specifies:
+#
+#      Whether or not proxy authentication through Privoxy should
+#      work.
+#
+#  Type of value:
+#
+#      0 or 1
+#
+#  Default value:
+#
+#      0
+#
+#  Effect if unset:
+#
+#      Proxy authentication headers are removed.
+#
+#  Notes:
+#
+#      Privoxy itself does not support proxy authentication, but can
+#      allow clients to authenticate against Privoxy's parent proxy.
+#
+#      By default Privoxy (3.0.21 and later) don't do that and remove
+#      Proxy-Authorization headers in requests and Proxy-Authenticate
+#      headers in responses to make it harder for malicious sites to
+#      trick inexperienced users into providing login information.
+#
+#      If this option is enabled the headers are forwarded.
+#
+#      Enabling this option is not recommended if there is no parent
+#      proxy that requires authentication or if the local network
+#      between Privoxy and the parent proxy isn't trustworthy. If
+#      proxy authentication is only required for some requests, it is
+#      recommended to use a client header filter to remove the
+#      authentication headers for requests where they aren't needed.
+#
+enable-proxy-authentication-forwarding 0
+#
 #  5. FORWARDING
 #  ==============
 #
@@ -1726,7 +1768,7 @@ socket-timeout 300
 #
 #  Default value:
 #
-#      None
+#      128
 #
 #  Effect if unset:
 #
@@ -1762,6 +1804,13 @@ socket-timeout 300
 #      Obviously using this option only makes sense if you choose a
 #      limit below the one enforced by the operating system.
 #
+#      One most POSIX-compliant systems Privoxy can't properly deal
+#      with more than FD_SETSIZE file descriptors at the same time
+#      and has to reject connections if the limit is reached. This
+#      will likely change in a future version, but currently this
+#      limit can't be increased without recompiling Privoxy with a
+#      different FD_SETSIZE limit.
+#
 #  Examples:
 #
 #      max-client-connections 256