X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=f41ec0760bdc3b01bf931923240b7427b4d37094;hp=1557a6fd6370fda983616b54ca60c056bcdd0506;hb=706c8ab535b696ab96adbb76c17f8c94ffb56163;hpb=7a1e3d199c4da4bc5e6c2d1720f953fbccc898be diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 1557a6fd..f41ec076 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -1018,7 +1018,7 @@ actionsfile 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 4 # show tagging-related messages debug 8 # show header parsing debug 16 # log all data written to the network debug 32 # debug force feature @@ -1269,7 +1269,7 @@ actionsfile They can only be used if Privoxy has been compiled with IPv6 support. If you aren't sure if your version supports it, have a look at - http://config.privoxy.org/show-status. + http://config.privoxy.org/show-status. Some operating systems will prefer IPv6 to IPv4 addresses even if the @@ -3907,6 +3907,8 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t HTTPS inspection allows to filter encrypted requests. This is only supported when Privoxy has been built with FEATURE_HTTPS_INSPECTION. + If you aren't sure if your version supports it, have a look at + http://config.privoxy.org/show-status. @@ -4080,9 +4082,9 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t Notes: - This directive specifies the name of the CA key file - in ".pem" format. See the ca-cert-file - for a command to generate it. + This directive specifies the name of the CA key file in ".pem" format. + The ca-cert-file section contains + a command to generate it. @@ -4412,7 +4414,9 @@ AES128-SHA An example file can be downloaded from - https://curl.haxx.se/ca/cacert.pem. + https://curl.se/ca/cacert.pem. + If you want to create the file yourself, please see: + https://curl.se/docs/caextract.html.