X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fconfig.html;h=5cad65b767b7b00502457d2d1143b20a64bd0b2f;hp=7967f84c9bb68cee1e119ef58306ce2781fc28d3;hb=42c361793c45b0d5fc0c116707ca12b2f60f4c52;hpb=322389db65561716cdc35949eea8ae911f8a0aa8 diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html index 7967f84c..5cad65b7 100644 --- a/doc/webserver/user-manual/config.html +++ b/doc/webserver/user-manual/config.html @@ -1,4121 +1,4282 @@ - -
Again, the main configuration file is named config on - Linux/Unix/BSD and OS/2, and config.txt on Windows. - Configuration lines consist of an initial keyword followed by a list of - values, all separated by whitespace (any number of spaces or tabs). For - example:
confdir /etc/privoxy
-Assigns the value /etc/privoxy to the option - confdir and thus indicates that the configuration - directory is named "/etc/privoxy/".
All options in the config file except for confdir and - logdir are optional. Watch out in the below description - for what happens if you leave them unset.
The main config file controls all aspects of Privoxy's - operation that are not location dependent (i.e. they apply universally, no matter - where you may be surfing).
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 you block and why you do that, your policies, etc. -
Location of the Privoxy User Manual. -
A fully qualified URI
Unset
http://www.privoxy.org/version/user-manual/ - will be used, where version is the Privoxy version. -
The User Manual URI is the single best source of information on - Privoxy, and is used for help links from some - of the internal CGI pages. The manual itself is normally packaged with the - binary distributions, so you probably want to set this to a locally - installed copy. -
Examples: -
The best all purpose solution is simply to put the full local - PATH to where the User Manual is - located: -
user-manual /usr/share/doc/privoxy/user-manual |
The User Manual is then available to anyone with access to - Privoxy, by following the built-in URL: - http://config.privoxy.org/user-manual/ - (or the shortcut: http://p.p/user-manual/). -
If the documentation is not on the local system, it can be accessed - from a remote server, as: -
user-manual http://example.com/privoxy/user-manual/ |
Warning |
If set, this option should be the first option in the config - file, because it is used while the config file is being read - on start-up. - |
A URL to be displayed in the error page that users will see if access to an untrusted page is denied. -
URL
Unset
No links are displayed on the "untrusted" error page. -
The value of this option only matters if the experimental trust mechanism has been - activated. (See trustfile below.) -
If you use the trust mechanism, it is a good idea to write up some on-line - documentation about your trust policy and to specify the URL(s) here. - Use multiple times for multiple URLs. -
The URL(s) should be added to the trustfile as well, so users don't end up - locked out from the information on why they were locked out in the first place! -
An email address to reach the Privoxy administrator. -
Email address
Unset
No email address is displayed on error pages and the CGI user interface. -
If both admin-address and proxy-info-url - are unset, the whole "Local Privoxy Support" box on all generated pages will - not be shown. -
A URL to documentation about the local Privoxy setup, - configuration or policies. -
URL
Unset
No link to local documentation is displayed on error pages and the CGI user interface. -
If both admin-address and proxy-info-url - are unset, the whole "Local Privoxy Support" box on all generated pages will - not be shown. -
This URL shouldn't be blocked ;-) -
Privoxy can (and normally does) use a number of - other files for additional configuration, help and logging. - This section of the configuration file tells Privoxy - where to find those other files.
The user running Privoxy, must have read - permission for all configuration files, and write permission to any files - that would be modified, such as log files and actions files.
The directory where the other configuration files are located.
Path name
/etc/privoxy (Unix) or Privoxy installation dir (Windows)
Mandatory
No trailing "/", please. -
An alternative directory where the templates are loaded from.
Path name
unset
The templates are assumed to be located in confdir/template.
Privoxy's original templates are usually - overwritten with each update. Use this option to relocate customized - templates that should be kept. As template variables might change - between updates, you shouldn't expect templates to work with - Privoxy releases other than the one - they were part of, though. -
The directory where all logging takes place - (i.e. where the logfile is located). -
Path name
/var/log/privoxy (Unix) or Privoxy installation dir (Windows)
Mandatory
No trailing "/", please. -
The actions file(s) to use -
Complete file name, relative to confdir
match-all.action # Actions that are applied to all sites and maybe overruled later on. - |
default.action # Main actions file - |
user.action # User customizations - |
No actions are taken at all. More or less neutral proxying. -
Multiple actionsfile lines are permitted, and are in fact recommended! -
- The default values are default.action, which is the - "main" actions file maintained by the developers, and - user.action, where you can make your personal additions. -
- Actions files contain all the per site and per URL configuration for - ad blocking, cookie management, privacy considerations, etc. - There is no point in using Privoxy without at - least one actions file. -
Note that since Privoxy 3.0.7, the complete filename, including the ".action" - extension has to be specified. The syntax change was necessary to be consistent - with the other file options and to allow previously forbidden characters. -
The filter file(s) to use -
File name, relative to confdir
default.filter (Unix) or default.filter.txt (Windows)
No textual content filtering takes place, i.e. all - +filter{name} - actions in the actions files are turned neutral. -
Multiple filterfile lines are permitted. -
The filter files contain content modification - rules that use regular expressions. These rules permit - powerful changes on the content of Web pages, and optionally the headers - as well, e.g., you could try to disable your favorite JavaScript annoyances, - re-write the actual displayed text, or just have some fun - playing buzzword bingo with web pages. -
The - +filter{name} - actions rely on the relevant filter (name) - to be defined in a filter file! -
A pre-defined filter file called default.filter that contains - a number of useful filters for common problems is included in the distribution. - See the section on the filter - action for a list. -
It is recommended to place any locally adapted filters into a separate - file, such as user.filter. -
The log file to use -
File name, relative to logdir
Unset (commented out). When activated: logfile (Unix) or privoxy.log (Windows).
No logfile is written. -
The logfile is where all logging and error messages are written. The level - of detail and number of messages are set with the debug - option (see below). The logfile can be useful for tracking down a problem with - Privoxy (e.g., it's not blocking an ad you - think it should block) and it can help you to monitor what your browser - is doing. -
Depending on the debug options below, the logfile may be a privacy risk - if third parties can get access to it. As most users will never look - at it, Privoxy 3.0.7 and later only log fatal - errors by default. -
For most troubleshooting purposes, you will have to change that, - please refer to the debugging section for details. -
Your logfile will grow indefinitely, and you will probably want to - periodically remove it. On Unix systems, you can do this with a cron job - (see "man cron"). For Red Hat based Linux distributions, a - logrotate script has been included. -
Any log files must be writable by whatever user Privoxy - is being run as (on Unix, default user id is "privoxy"). -
The name of the trust file to use -
File name, relative to confdir
Unset (commented out). When activated: trust (Unix) or trust.txt (Windows)
The entire trust mechanism is disabled. -
The trust mechanism is an experimental feature for building white-lists and should - be used with care. It is NOT recommended for the casual user. -
If you specify a trust file, Privoxy will only allow - access to sites that are specified in the trustfile. Sites can be listed - in one of two ways: -
Prepending a ~ character limits access to this site - only (and any sub-paths within this site), e.g. - ~www.example.com allows access to - ~www.example.com/features/news.html, etc. -
Or, you can designate sites as trusted referrers, by - prepending the name with a + character. The effect is that - access to untrusted sites will be granted -- but only if a link from this - trusted referrer was used to get there. The link target will then be added - to the "trustfile" so that future, direct accesses will be - granted. Sites added via this mechanism do not become trusted referrers - themselves (i.e. they are added with a ~ designation). - There is a limit of 512 such entries, after which new entries will not be - made. -
If you use the + operator in the trust file, it may grow - considerably over time. -
It is recommended that Privoxy be compiled with - the --disable-force, --disable-toggle and - --disable-editor options, if this feature is to be - used. -
Possible applications include limiting Internet access for children. -
These options are mainly useful when tracing a problem. - Note that you might also want to invoke - Privoxy with the --no-daemon - command line option when debugging. -
Key values that determine what information gets logged. -
Integer values
0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
Default value is used (see above). -
The available debug levels are: -
debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. + + + ++ |
+
+ You would then need to change your browser's proxy settings to + squid's address and port. Squid + normally uses port 3128. If unsure consult http_port in squid.conf. +
++ You could just as well decide to only forward requests you + suspect of leading to Windows executables through a + virus-scanning parent proxy, say, on antivir.example.com, port 8010: +
++
+
++ forward / . + forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010 ++ |
+
+ How often Privoxy retries if a forwarded connection request + fails. +
++ Number of retries. +
++ 0 +
++ Connections forwarded through other proxies are treated + like direct connections and no retry attempts are made. +
++ forwarded-connect-retries is + mainly interesting for socks4a connections, where Privoxy can't detect why the + connections failed. The connection might have failed + because of a DNS timeout in which case a retry makes sense, + but it might also have failed because the server doesn't + exist or isn't reachable. In this case the retry will just + delay the appearance of Privoxy's error message. +
++ Note that in the context of this option, "forwarded connections" includes all + connections that Privoxy forwards through other proxies. + This option is not limited to the HTTP CONNECT method. +
++ Only use this option, if you are getting lots of + forwarding-related error messages that go away when you try + again manually. Start with a small value and check + Privoxy's logfile from time to time, to see how many + retries are usually needed. +
++ forwarded-connect-retries 1 +
++ Whether intercepted requests should be treated as valid. +
++ 0 or 1 +
++ 0 +
++ Only proxy requests are accepted, intercepted requests are + treated as invalid. +
++ If you don't trust your clients and want to force them to + use Privoxy, enable this + option and configure your packet filter to redirect + outgoing HTTP connections into Privoxy. +
++ Note that intercepting encrypted connections (HTTPS) isn't + supported. +
++ Make sure that Privoxy's + own requests aren't redirected as well. Additionally take + care that Privoxy can't + intentionally connect to itself, otherwise you could run + into redirection loops if Privoxy's listening port is reachable + by the outside or an attacker has access to the pages you + visit. +
++ If you are running Privoxy as intercepting proxy without + being able to intercept all client requests you may want to + adjust the CGI templates to make sure they don't reference + content from config.privoxy.org. +
++ accept-intercepted-requests 1 +
++ Whether requests to Privoxy's CGI pages can be blocked or + redirected. +
++ 0 or 1 +
++ 0 +
++ Privoxy ignores block and + redirect actions for its CGI pages. +
++ By default Privoxy ignores + block or redirect actions for its CGI pages. Intercepting + these requests can be useful in multi-user setups to + implement fine-grained access control, but it can also + render the complete web interface useless and make + debugging problems painful if done without care. +
++ Don't enable this option unless you're sure that you really + need it. +
++ allow-cgi-request-crunching 1 +
++ Whether the CGI interface should stay compatible with + broken HTTP clients. +
++ 0 or 1 +
++ 0 +
++ The CGI form generate long GET URLs. +
++ Privoxy's CGI forms can + lead to rather long URLs. This isn't a problem as far as + the HTTP standard is concerned, but it can confuse clients + with arbitrary URL length limitations. +
++ Enabling split-large-forms causes Privoxy to divide big forms into + smaller ones to keep the URL length down. It makes editing + a lot less convenient and you can no longer submit all + changes at once, but at least it works around this browser + bug. +
++ If you don't notice any editing problems, there is no + reason to enable this option, but if one of the submit + buttons appears to be broken, you should give it a try. +
++ split-large-forms 1 +
++ Number of seconds after which an open connection will no + longer be reused. +
++ Time in seconds. +
++ None +
++ Connections are not kept alive. +
++ This option allows clients to keep the connection to Privoxy alive. If the server + supports it, Privoxy will + keep the connection to the server alive as well. Under + certain circumstances this may result in speed-ups. +
++ By default, Privoxy will + close the connection to the server if the client connection + gets closed, or if the specified timeout has been reached + without a new request coming in. This behaviour can be + changed with the connection-sharing option. +
++ This option has no effect if Privoxy has been compiled without + keep-alive support. +
++ Note that a timeout of five seconds as used in the default + configuration file significantly decreases the number of + connections that will be reused. The value is used because + some browsers limit the number of connections they open to + a single host and apply the same limit to proxies. This can + result in a single website "grabbing" all the connections the browser + allows, which means connections to other websites can't be + opened until the connections currently in use time out. +
++ Several users have reported this as a Privoxy bug, so the + default value has been reduced. Consider increasing it to + 300 seconds or even more if you think your browser can + handle it. If your browser appears to be hanging, it + probably can't. +
++ keep-alive-timeout 300 +
++ Whether or not pipelined requests should be served. +
++ 0 or 1. +
++ None +
++ If Privoxy receives more than one request at once, it + terminates the client connection after serving the first + one. +
++ Privoxy currently doesn't + pipeline outgoing requests, thus allowing pipelining on the + client connection is not guaranteed to improve the + performance. +
++ By default Privoxy tries + to discourage clients from pipelining by discarding + aggressively pipelined requests, which forces the client to + resend them through a new connection. +
++ This option lets Privoxy + tolerate pipelining. Whether or not that improves + performance mainly depends on the client configuration. +
++ If you are seeing problems with pages not properly loading, + disabling this option could work around the problem. +
++ tolerate-pipelining 1 +
++ Assumed server-side keep-alive timeout if not specified by + the server. +
++ Time in seconds. +
++ None +
++ Connections for which the server didn't specify the + keep-alive timeout are not reused. +
++ Enabling this option significantly increases the number of + connections that are reused, provided the keep-alive-timeout + option is also enabled. +
++ While it also increases the number of connections problems + when Privoxy tries to + reuse a connection that already has been closed on the + server side, or is closed while Privoxy is trying to reuse it, this + should only be a problem if it happens for the first + request sent by the client. If it happens for requests on + reused client connections, Privoxy will simply close the + connection and the client is supposed to retry the request + without bothering the user. +
++ Enabling this option is therefore only recommended if the + connection-sharing option is disabled. +
++ It is an error to specify a value larger than the keep-alive-timeout + value. +
++ This option has no effect if Privoxy has been compiled without + keep-alive support. +
++ default-server-timeout 60 +
++ Whether or not outgoing connections that have been kept + alive should be shared between different incoming + connections. +
++ 0 or 1 +
++ None +
++ Connections are not shared. +
++ This option has no effect if Privoxy has been compiled without + keep-alive support, or if it's disabled. +
++ Note that reusing connections doesn't necessary cause + speedups. There are also a few privacy implications you + should be aware of. +
++ If this option is effective, outgoing connections are + shared between clients (if there are more than one) and + closing the browser that initiated the outgoing connection + does no longer affect the connection between Privoxy and the server unless the + client's request hasn't been completed yet. +
++ If the outgoing connection is idle, it will not be closed + until either Privoxy's or + the server's timeout is reached. While it's open, the + server knows that the system running Privoxy is still there. +
++ If there are more than one client (maybe even belonging to + multiple users), they will be able to reuse each others + connections. This is potentially dangerous in case of + authentication schemes like NTLM where only the connection + is authenticated, instead of requiring authentication for + each request. +
++ If there is only a single client, and if said client can + keep connections alive on its own, enabling this option has + next to no effect. If the client doesn't support connection + keep-alive, enabling this option may make sense as it + allows Privoxy to keep + outgoing connections alive even if the client itself + doesn't support it. +
++ You should also be aware that enabling this option + increases the likelihood of getting the "No server or + forwarder data" error message, especially if you are using + a slow connection to the Internet. +
++ This option should only be used by experienced users who + understand the risks and can weight them against the + benefits. +
++ connection-sharing 1 +
++ Number of seconds after which a socket times out if no data + is received. +
++ Time in seconds. +
++ None +
++ A default value of 300 seconds is used. +
++ The default is quite high and you probably want to reduce + it. If you aren't using an occasionally slow proxy like + Tor, reducing it to a few seconds should be fine. +
++ socket-timeout 300 +
++ Maximum number of client connections that will be served. +
++ Positive number. +
++ 128 +
++ Connections are served until a resource limit is reached. +
++ Privoxy creates one thread + (or process) for every incoming client connection that + isn't rejected based on the access control settings. +
++ If the system is powerful enough, Privoxy can theoretically deal with + several hundred (or thousand) connections at the same time, + but some operating systems enforce resource limits by + shutting down offending processes and their default limits + may be below the ones Privoxy would require under heavy + load. +
++ Configuring Privoxy to + enforce a connection limit below the thread or process + limit used by the operating system makes sure this doesn't + happen. Simply increasing the operating system's limit + would work too, but if Privoxy isn't the only application + running on the system, you may actually want to limit the + resources used by Privoxy. +
++ If Privoxy is only used by + a single trusted user, limiting the number of client + connections is probably unnecessary. If there are multiple + possibly untrusted users you probably still want to + additionally use a packet filter to limit the maximal + number of incoming connections per client. Otherwise a + malicious user could intentionally create a high number of + connections to prevent other users from using Privoxy. +
++ 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. +
++ max-client-connections 256 +
++ The status code Privoxy returns for pages blocked with +handle-as-empty-document. +
++ 0 or 1 +
++ 0 +
++ Privoxy returns a status 403(forbidden) for all blocked + pages. +
++ Privoxy returns a status 200(OK) for pages blocked with + +handle-as-empty-document and a status 403(Forbidden) for + all other blocked pages. +
++ This directive was added as a work-around for Firefox bug + 492459: "Websites are no longer + rendered if SSL requests for JavaScripts are blocked by a + proxy." (https://bugzilla.mozilla.org/show_bug.cgi?id=492459), + the bug has been fixed for quite some time, but this + directive is also useful to make it harder for websites to + detect whether or not resources are being blocked. +
++ Whether or not buffered content is compressed before + delivery. +
++ 0 or 1 +
++ 0 +
++ Privoxy does not compress buffered content. +
++ Privoxy compresses buffered content before delivering it to + the client, provided the client supports it. +
++ This directive is only supported if Privoxy has been + compiled with FEATURE_COMPRESSION, which should not to be + confused with FEATURE_ZLIB. +
++ Compressing buffered content is mainly useful if Privoxy + and the client are running on different systems. If they + are running on the same system, enabling compression is + likely to slow things down. If you didn't measure + otherwise, you should assume that it does and keep this + option disabled. +
++ Privoxy will not compress buffered content below a certain + length. +
++ The compression level that is passed to the zlib library + when compressing buffered content. +
++ Positive number ranging from 0 + to 9. +
++ 1 +
++ Compressing the data more takes usually longer than + compressing it less or not compressing it at all. Which + level is best depends on the connection between Privoxy and + the client. If you can't be bothered to benchmark it for + yourself, you should stick with the default and keep + compression disabled. +
++ If compression is disabled, the compression level is + irrelevant. +
++
+
++ # Best speed (compared to the other levels) + compression-level 1 + # Best compression + compression-level 9 + # No compression. Only useful for testing as the added header + # slightly increases the amount of data that has to be sent. + # If your benchmark shows that using this compression level + # is superior to using no compression at all, the benchmark + # is likely to be flawed. + compression-level 0 + ++ |
+
+ The order in which client headers are sorted before + forwarding them. +
++ Client header names delimited by + spaces or tabs +
++ None +
++ By default Privoxy leaves + the client headers in the order they were sent by the + client. Headers are modified in-place, new headers are + added at the end of the already existing headers. +
++ The header order can be used to fingerprint client requests + independently of other headers like the User-Agent. +
++ This directive allows to sort the headers differently to + better mimic a different User-Agent. Client headers will be + emitted in the order given, headers whose name isn't + explicitly specified are added at the end. +
++ Note that sorting headers in an uncommon way will make + fingerprinting actually easier. Encrypted headers are not + affected by this directive. +
++ The name of a tag that will always be set for clients that + requested it through the webinterface. +
++ Tag name followed by a + description that will be shown in the webinterface +
++ None +
++ Warning + | +
+ + This is an experimental feature. The syntax is + likely to change in future versions. + + |
+
+ Client-specific tags allow Privoxy admins to create + different profiles and let the users chose which one they + want without impacting other users. +
++ One use case is allowing users to circumvent certain blocks + without having to allow them to circumvent all blocks. This + is not possible with the enable-remote-toggle + feature because it would bluntly disable all blocks for + all users and also affect other actions like filters. It + also is set globally which renders it useless in most + multi-user setups. +
++ After a client-specific tag has been defined with the + client-specific-tag directive, action sections can be + activated based on the tag by using a CLIENT-TAG pattern. The CLIENT-TAG pattern is + evaluated at the same priority as URL patterns, as a result + the last matching pattern wins. Tags that are created based + on client or server headers are evaluated later on and can + overrule CLIENT-TAG and URL patterns! +
++ The tag is set for all requests that come from clients that + requested it to be set. Note that "clients" are + differentiated by IP address, if the IP address changes the + tag has to be requested again. +
++ Clients can request tags to be set by using the CGI + interface http://config.privoxy.org/client-tags. + The specific tag description is only used on the web page + and should be phrased in away that the user understand the + effect of the tag. +
++
+
++ # Define a couple of tags, the described effect requires action sections + # that are enabled based on CLIENT-TAG patterns. + client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions + disable-content-filters Disable content-filters but do not affect other actions + ++ |
+
+ How long a temporarily enabled tag remains enabled. +
++ Time in seconds. +
++ 60 +
++ Warning + | +
+ + This is an experimental feature. The syntax is + likely to change in future versions. + + |
+
+ In case of some tags users may not want to enable them + permanently, but only for a short amount of time, for + example to circumvent a block that is the result of an + overly-broad URL pattern. +
++ The CGI interface http://config.privoxy.org/client-tags therefore + provides a "enable this tag temporarily" option. If it is + used, the tag will be set until the client-tag-lifetime is + over. +
++
+
++ # Increase the time to life for temporarily enabled tags to 3 minutes + client-tag-lifetime 180 + ++ |
+
+ Whether or not Privoxy should use IP addresses specified + with the X-Forwarded-For header +
++ 0 or one +
++ 0 +
++ Warning + | +
+ + This is an experimental feature. The syntax is + likely to change in future versions. + + |
+
+ If clients reach Privoxy through another proxy, for example + a load balancer, Privoxy can't tell the client's IP address + from the connection. If multiple clients use the same + proxy, they will share the same client tag settings which + is usually not desired. +
++ This option lets Privoxy use the X-Forwarded-For header + value as client IP address. If the proxy sets the header, + multiple clients using the same proxy do not share the same + client tag settings. +
++ This option should only be enabled if Privoxy can only be + reached through a proxy and if the proxy can be trusted to + set the header correctly. It is recommended that ACL are + used to make sure only trusted systems can reach Privoxy. +
++ If access to Privoxy isn't limited to trusted systems, this + option would allow malicious clients to change the client + tags for other clients or increase Privoxy's memory + requirements by registering lots of client tag settings for + clients that don't exist. +
++
+
++ # Allow systems that can reach Privoxy to provide the client + # IP address with a X-Forwarded-For header. + trust-x-forwarded-for 1 + ++ |
+
+ 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 copies log messages to the + console window. The log detail depends on the debug directive. +
++
+
+ 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). +
++ Warning: Setting this to 0 will result in the buffer to grow + 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. +
++
+
+ #hide-console
+
+