X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fconfig.html;h=7967f84c9bb68cee1e119ef58306ce2781fc28d3;hb=b8b189fe71adc144bc77ea0126cd7bf4bbe07d69;hp=d46960a4133da66144629675003bce956dac8242;hpb=1c0834f3f9f6b68c694319ea2e0b9327ba814507;p=privoxy.git diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html index d46960a4..7967f84c 100644 --- a/doc/webserver/user-manual/config.html +++ b/doc/webserver/user-manual/config.html @@ -363,7 +363,13 @@ CLASS="VARIABLELIST" >Default value:
Two example URLs are provided
Unsetstandard.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 @@ -1369,10 +1371,10 @@ WIDTH="90%" >
debug 1 # log each request destination (and the crunch reason if debug 1 # Log the destination for each request Privoxy intercepted the request)
+> let through. See also debug 1024.
debug 2 # show each connection status
debug 4 # show I/O status
debug 8 # show header parsing
@@ -1382,6 +1384,10 @@ CLASS="APPLICATION"
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 errors
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. +
Note that reusing connections doesn't necessary cause speedups. + There are also a few privacy implications you should be aware of. +
Outgoing connections are shared between clients (if there are more + than one) and closing the client that initiated the outgoing connection + does not 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. +
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 +