X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=427483216f2addef8afc218d276d0cf40f53c14b;hp=e2b205bc5c6d5e0527431f2a10e3069074af00d2;hb=c1c254de39540a55a837a6ab24b6a4ce22fc7fa2;hpb=100f48795eee7d2996bff48871bf745af01811c7 diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index e2b205bc..42748321 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -1016,7 +1016,7 @@ actionsfile The available debug levels are: - debug 1 # Log the destination for each request &my-app; let through. See also debug 1024. + debug 1 # Log the destination for each request. See also debug 1024. debug 2 # show each connection status debug 4 # show I/O status debug 8 # show header parsing @@ -1677,7 +1677,7 @@ ACLs: permit-access and deny-access If your system implements RFC 3493, then src_addr and dst_addr can be IPv6 addresses delimeted by + class="parameter">dst_addr can be IPv6 addresses delimited by brackets, port can be a number or a service name, and src_masklen and @@ -3235,13 +3235,13 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Under high load incoming connection may queue up before Privoxy - gets around to serve them. The queue length is limitted by the + gets around to serve them. The queue length is limited by the operating system. Once the queue is full, additional connections are dropped before Privoxy can accept and serve them. Increasing the queue length allows Privoxy to accept more - incomming connections that arrive roughly at the same time. + incoming connections that arrive roughly at the same time. Note that Privoxy can only request a certain queue length, @@ -3901,7 +3901,7 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t -TLS/SSL +TLS/SSL Inspection @@ -4164,7 +4164,7 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Specifies: - Directory to safe generated keys and certificates. + Directory to save generated keys and certificates.