projects
/
privoxy.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Mention that HTTPS inspection also allows to filter encrypted responses
[privoxy.git]
/
doc
/
source
/
p-config.sgml
diff --git
a/doc/source/p-config.sgml
b/doc/source/p-config.sgml
index
e9e8310
..
4e001ad
100644
(file)
--- a/
doc/source/p-config.sgml
+++ b/
doc/source/p-config.sgml
@@
-1018,7
+1018,7
@@
actionsfile
<programlisting>
debug 1 # Log the destination for each request. See also debug 1024.
debug 2 # show each connection status
<programlisting>
debug 1 # Log the destination for each request. See also debug 1024.
debug 2 # show each connection status
- debug 4 # show
I/O statu
s
+ debug 4 # show
tagging-related message
s
debug 8 # show header parsing
debug 16 # log all data written to the network
debug 32 # debug force feature
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 <application>Privoxy</application> has
been compiled with IPv6 support. If you aren't sure if your version
supports it, have a look at
They can only be used if <application>Privoxy</application> has
been compiled with IPv6 support. If you aren't sure if your version
supports it, have a look at
- <
literal>http://config.privoxy.org/show-status</literal
>.
+ <
ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink
>.
</para>
<para>
Some operating systems will prefer IPv6 to IPv4 addresses even if the
</para>
<para>
Some operating systems will prefer IPv6 to IPv4 addresses even if the
@@
-3904,9
+3904,11
@@
forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
<title>HTTPS Inspection (Experimental)</title>
<para>
<title>HTTPS Inspection (Experimental)</title>
<para>
- HTTPS inspection allows to filter encrypted requests.
+ HTTPS inspection allows to filter encrypted requests
and responses
.
This is only supported when <application>Privoxy</application>
has been built with FEATURE_HTTPS_INSPECTION.
This is only supported when <application>Privoxy</application>
has been built with FEATURE_HTTPS_INSPECTION.
+ If you aren't sure if your version supports it, have a look at
+ <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
</para>
<!-- ~~~~~ New section ~~~~~ -->
</para>
<!-- ~~~~~ New section ~~~~~ -->
@@
-4024,7
+4026,7
@@
forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
</para>
<para>
The file can be generated with:
</para>
<para>
The file can be generated with:
- openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.crt -days 3650
+ <command>openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.crt -days 3650</command>
</para>
</listitem>
</varlistentry>
</para>
</listitem>
</varlistentry>
@@
-4080,9
+4082,9
@@
forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
<term>Notes:</term>
<listitem>
<para>
<term>Notes:</term>
<listitem>
<para>
- This directive specifies the name of the CA key file
- in ".pem" format. See the <ulink url="#CA-CERT-FILE">ca-cert-file</ulink>
-
for
a command to generate it.
+ This directive specifies the name of the CA key file
in ".pem" format.
+ The <ulink url="#CA-CERT-FILE">ca-cert-file section</ulink> contains
+ a command to generate it.
</para>
</listitem>
</varlistentry>
</para>
</listitem>
</varlistentry>
@@
-4412,7
+4414,9
@@
AES128-SHA
</para>
<para>
An example file can be downloaded from
</para>
<para>
An example file can be downloaded from
- <ulink url="https://curl.haxx.se/ca/cacert.pem">https://curl.haxx.se/ca/cacert.pem</ulink>.
+ <ulink url="https://curl.se/ca/cacert.pem">https://curl.se/ca/cacert.pem</ulink>.
+ If you want to create the file yourself, please see:
+ <ulink url="https://curl.se/docs/caextract.html">https://curl.se/docs/caextract.html</ulink>.
</para>
</listitem>
</varlistentry>
</para>
</listitem>
</varlistentry>