Two example URLs are provided
UnsetThe directory where all logging takes place - (i.e. where logfile and - jarfile are located). +> is located).
standard.action # Internal purposes, no editing recommended
match-all.action # Actions that are applied to all sites and maybe overruled later on.default.action # Main actions file
default.action # Main actions fileuser.action # User customizations
user.action # User customizations
- The default values include standard.action, which is used
- for internal purposes and should be loaded, default.action,
- which is the , which is the
+ "main" actions file maintained by the developers, and
@@ -1155,79 +1153,8 @@ CLASS="SECT3"
> The file to store intercepted cookies in
- File name, relative to logdir Unset (commented out). When activated: jarfile (Unix) or privoxy.jar (Windows). Intercepted cookies are not stored in a dedicated log file.
- 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.
- The hostname shown on the CGI pages.
+ Text Unset The hostname provided by the operating system is used.
+ On some misconfigured systems resolving the hostname fails or
+ takes too much time and slows Privoxy down. Setting a fixed hostname
+ works around the problem.
+ In other circumstances it might be desirable to show a hostname
+ other than the one returned by the operating system. For example
+ if the system has several different hostnames and you don't want
+ to use the first one.
+ Note that Privoxy does not validate the specified hostname value.
+ Number of seconds after which an open connection will no longer be reused.
+ Time in seconds.
+ None Connections are not reused.
+ This option has no effect if Privoxy
+ has been compiled without keep-alive support.
+ keep-alive-timeout 300
+ 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.
+ For SOCKS requests the timeout currently doesn't start until
+ the SOCKS server accepted the request. This will be fixed in
+ the next release.
+ socket-timeout 300
+ 7.2.7. jarfile
7.2.8. trustfile7.2.7. trustfile
debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
- debug 2 # show each connection status
- debug 4 # show I/O status
- debug 8 # show header parsing
- debug 16 # log all data written to the network into the logfile
- debug 32 # debug force feature
- debug 64 # debug regular expression filters
- debug 128 # debug redirects
- debug 256 # debug GIF de-animation
- debug 512 # Common Log Format
- debug 1024 # debug kill pop-ups
- debug 2048 # CGI user interface
- debug 4096 # Startup banner and warnings.
- debug 8192 # Non-fatal errors debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
+ debug 2 # show each connection status
+ debug 4 # show I/O status
+ debug 8 # show header parsing
+ debug 16 # log all data written to the network into the logfile
+ debug 32 # debug force feature
+ debug 64 # debug regular expression filters
+ debug 128 # debug redirects
+ debug 256 # debug GIF de-animation
+ debug 512 # Common Log Format
+ debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
+ debug 2048 # CGI user interface
+ debug 4096 # Startup banner and warnings.
+ debug 8192 # Non-fatal errors7.3.3. hostname
7.5.8. keep-alive-timeout
7.5.9. socket-timeout