X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=config;h=33691aba1616fb74a9fca543e3919c668f906083;hb=1c0834f3f9f6b68c694319ea2e0b9327ba814507;hp=32e51573cecae817e0287d340215cc17e5e90e9a;hpb=0a270e02b4f0dafab5cb075616db21e9b3f7a126;p=privoxy.git

diff --git a/config b/config
index 32e51573..33691aba 100644
--- a/config
+++ b/config
@@ -1,6 +1,6 @@
-#        Sample Configuration File for Privoxy v3.0.9
+#        Sample Configuration File for Privoxy v3.0.11
 #
-#  $Id: p-config.sgml,v 2.30 2008/03/27 18:31:20 fabiankeil Exp $
+#  $Id: p-config.sgml,v 2.32 2008/08/30 12:03:09 fabiankeil Exp $
 #
 #  Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
 #
@@ -70,6 +70,7 @@
 #
 #
 #  1. LOCAL SET-UP DOCUMENTATION
+#  ==============================
 #
 #  If you intend to operate Privoxy for more users than just yourself,
 #  it might be a good idea to let them know how to reach you, what
@@ -78,6 +79,7 @@
 #
 #
 #  1.1. user-manual
+#  =================
 #
 #  Specifies:
 #
@@ -132,6 +134,7 @@
 #
 #
 #  1.2. trust-info-url
+#  ====================
 #
 #  Specifies:
 #
@@ -168,6 +171,7 @@ trust-info-url  http://www.example.com/what_we_allow.html
 #
 #
 #  1.3. admin-address
+#  ===================
 #
 #  Specifies:
 #
@@ -196,6 +200,7 @@ trust-info-url  http://www.example.com/what_we_allow.html
 #
 #
 #  1.4. proxy-info-url
+#  ====================
 #
 #  Specifies:
 #
@@ -227,6 +232,7 @@ trust-info-url  http://www.example.com/what_we_allow.html
 #
 #
 #  2. CONFIGURATION AND LOG FILE LOCATIONS
+#  ========================================
 #
 #  Privoxy can (and normally does) use a number of other files for
 #  additional configuration, help and logging. This section of the
@@ -239,6 +245,7 @@ trust-info-url  http://www.example.com/what_we_allow.html
 #
 #
 #  2.1. confdir
+#  =============
 #
 #  Specifies:
 #
@@ -264,6 +271,7 @@ confdir .
 #
 #
 #  2.2. templdir
+#  ==============
 #
 #  Specifies:
 #
@@ -293,11 +301,12 @@ confdir .
 #
 #
 #  2.3. logdir
+#  ============
 #
 #  Specifies:
 #
-#      The directory where all logging takes place (i.e. where logfile
-#      and jarfile are located).
+#      The directory where all logging takes place (i.e. where the
+#      logfile is located).
 #
 #  Type of value:
 #
@@ -319,6 +328,7 @@ logdir .
 #
 #
 #  2.4. actionsfile
+#  =================
 #
 #  Specifies:
 #
@@ -366,6 +376,7 @@ actionsfile user.action      # User customizations
 #
 #
 #  2.5. filterfile
+#  ================
 #
 #  Specifies:
 #
@@ -410,6 +421,7 @@ filterfile default.filter
 #
 #
 #  2.6. logfile
+#  =============
 #
 #  Specifies:
 #
@@ -456,39 +468,8 @@ filterfile default.filter
 logfile logfile
 #
 #
-#  2.7. jarfile
-#
-#  Specifies:
-#
-#      The file to store intercepted cookies in
-#
-#  Type of value:
-#
-#      File name, relative to logdir
-#
-#  Default value:
-#
-#      Unset (commented out). When activated: jarfile (Unix) or
-#      privoxy.jar (Windows).
-#
-#  Effect if unset:
-#
-#      Intercepted cookies are not stored in a dedicated log file.
-#
-#  Notes:
-#
-#      The jarfile may grow to ridiculous sizes over time.
-#
-#      If debug 8 (show header parsing) is enabled, cookies are also
-#      written to the logfile with the rest of the headers. Therefore
-#      this option isn't very useful and may be removed in future
-#      releases. Please report to the developers if you are still
-#      using it.
-#
-#jarfile jarfile
-#
-#
-#  2.8. trustfile
+#  2.7. trustfile
+#  ===============
 #
 #  Specifies:
 #
@@ -545,6 +526,7 @@ logfile logfile
 #
 #
 #  3. DEBUGGING
+#  =============
 #
 #  These options are mainly useful when tracing a problem. Note that
 #  you might also want to invoke Privoxy with the --no-daemon command
@@ -553,6 +535,7 @@ logfile logfile
 #
 #
 #  3.1. debug
+#  ===========
 #
 #  Specifies:
 #
@@ -624,6 +607,7 @@ logfile logfile
 #
 #
 #  3.2. single-threaded
+#  =====================
 #
 #  Specifies:
 #
@@ -651,6 +635,7 @@ logfile logfile
 #
 #
 #  3.3. hostname
+#  ==============
 #
 #  Specifies:
 #
@@ -685,6 +670,7 @@ logfile logfile
 #
 #
 #  4. ACCESS CONTROL AND SECURITY
+#  ===============================
 #
 #  This section of the config file controls the security-relevant
 #  aspects of Privoxy's configuration.
@@ -692,6 +678,7 @@ logfile logfile
 #
 #
 #  4.1. listen-address
+#  ====================
 #
 #  Specifies:
 #
@@ -744,6 +731,7 @@ listen-address  127.0.0.1:8118
 #
 #
 #  4.2. toggle
+#  ============
 #
 #  Specifies:
 #
@@ -775,6 +763,7 @@ toggle  1
 #
 #
 #  4.3. enable-remote-toggle
+#  ==========================
 #
 #  Specifies:
 #
@@ -816,6 +805,7 @@ enable-remote-toggle  0
 #
 #
 #  4.4. enable-remote-http-toggle
+#  ===============================
 #
 #  Specifies:
 #
@@ -854,6 +844,7 @@ enable-remote-http-toggle  0
 #
 #
 #  4.5. enable-edit-actions
+#  =========================
 #
 #  Specifies:
 #
@@ -894,6 +885,7 @@ enable-edit-actions 0
 #
 #
 #  4.6. enforce-blocks
+#  ====================
 #
 #  Specifies:
 #
@@ -942,6 +934,7 @@ enforce-blocks 0
 #
 #
 #  4.7. ACLs: permit-access and deny-access
+#  =========================================
 #
 #  Specifies:
 #
@@ -1026,6 +1019,7 @@ enforce-blocks 0
 #
 #
 #  4.8. buffer-limit
+#  ==================
 #
 #  Specifies:
 #
@@ -1061,6 +1055,7 @@ buffer-limit 4096
 #
 #
 #  5. FORWARDING
+#  ==============
 #
 #  This feature allows routing of HTTP requests through a chain of
 #  multiple proxies.
@@ -1083,6 +1078,7 @@ buffer-limit 4096
 #
 #
 #  5.1. forward
+#  =============
 #
 #  Specifies:
 #
@@ -1134,6 +1130,7 @@ buffer-limit 4096
 #
 #
 #  5.2. forward-socks4, forward-socks4a and forward-socks5
+#  ========================================================
 #
 #  Specifies:
 #
@@ -1224,6 +1221,7 @@ buffer-limit 4096
 #
 #
 #  5.3. forwarded-connect-retries
+#  ===============================
 #
 #  Specifies:
 #
@@ -1270,6 +1268,7 @@ forwarded-connect-retries  0
 #
 #
 #  5.4. accept-intercepted-requests
+#  =================================
 #
 #  Specifies:
 #
@@ -1308,6 +1307,7 @@ accept-intercepted-requests 0
 #
 #
 #  5.5. allow-cgi-request-crunching
+#  =================================
 #
 #  Specifies:
 #
@@ -1345,6 +1345,7 @@ allow-cgi-request-crunching 0
 #
 #
 #  5.6. split-large-forms
+#  =======================
 #
 #  Specifies:
 #
@@ -1386,21 +1387,22 @@ split-large-forms 0
 #
 #
 #  6. WINDOWS GUI OPTIONS
+#  =======================
 #
 #  Privoxy has a number of options specific to the Windows GUI
 #  interface:
 #
-
+#
 #  If "activity-animation" is set to 1, the Privoxy icon will animate
 #  when "Privoxy" is active. To turn off, set to 0.
 #
 #activity-animation   1
-
+#
 #  If "log-messages" is set to 1, Privoxy will log messages to the
 #  console window:
 #
 #log-messages   1
-
+#
 #  If "log-buffer-size" is set to 1, the size of the log buffer,
 #  i.e. the amount of memory used for the log messages displayed in
 #  the console window, will be limited to "log-max-lines" (see below).
@@ -1409,36 +1411,36 @@ split-large-forms 0
 #  infinitely and eat up all your memory!
 #
 #log-buffer-size 1
-
+#
 #  log-max-lines is the maximum number of lines held in the log
 #  buffer. See above.
 #
 #log-max-lines 200
-
+#
 #  If "log-highlight-messages" is set to 1, Privoxy will highlight
 #  portions of the log messages with a bold-faced font:
 #
 #log-highlight-messages 1
-
+#
 #  The font used in the console window:
 #
 #log-font-name Comic Sans MS
-
+#
 #  Font size used in the console window:
 #
 #log-font-size 8
-
+#
 #  "show-on-task-bar" controls whether or not Privoxy will appear as
 #  a button on the Task bar when minimized:
 #
 #show-on-task-bar 0
-
+#
 #  If "close-button-minimizes" is set to 1, the Windows close button
 #  will minimize Privoxy instead of closing the program (close with
 #  the exit option on the File menu).
 #
 #close-button-minimizes 1
-
+#
 #  The "hide-console" option is specific to the MS-Win console version
 #  of Privoxy.  If this option is used, Privoxy will disconnect from
 #  and hide the command console.