Purpose : Used with other docs and files only.
- Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
+ Copyright (C) 2001-2021 Privoxy Developers https://www.privoxy.org/
See LICENSE.
========================================================================
Sample Configuration File for Privoxy &p-version;
</title>
<para>
-Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
+Copyright (C) 2001-2021 Privoxy Developers https://www.privoxy.org/
</para>
<literallayout>
fk 2007-11-07
-->
<![%config-file;[<literallayout>@@actionsfile user.action # User customizations</literallayout>]]>
+<![%config-file;[<literallayout>@@#actionsfile regression-tests.action # Tests for privoxy-regression-test</literallayout>]]>
</sect3>
<!-- ~~~~~ New section ~~~~~ -->
</para>
<para>
Note that sorting headers in an uncommon way will make fingerprinting
- actually easier. Encrypted headers are not affected by this directive.
+ actually easier.
+ Encrypted headers are not affected by this directive unless
+ <literal><ulink url="actions-file.html#HTTPS-INSPECTION">https-inspection</ulink></literal>
+ is enabled.
</para>
</listitem>
</varlistentry>
Referer \
Cookie \
DNT \
+ Connection \
+ Pragma \
+ Upgrade-Insecure-Requests \
If-Modified-Since \
Cache-Control \
Content-Length \
+ Origin \
Content-Type
</literallayout>]]>
</sect3>
<varlistentry>
<term>Notes:</term>
<listitem>
- <warning>
- <para>
- This is an experimental feature. The syntax is likely to change
- in future versions.
- </para>
- </warning>
<para>
Client-specific tags allow Privoxy admins to create different
profiles and let the users chose which one they want without
Clients can request tags to be set by using the CGI interface <ulink
url="http://config.privoxy.org/client-tags">http://config.privoxy.org/client-tags</ulink>.
The specific tag description is only used on the web page and should
- be phrased in away that the user understand the effect of the tag.
+ be phrased in away that the user understands the effect of the tag.
</para>
</listitem>
</varlistentry>
# that are enabled based on CLIENT-TAG patterns.
client-specific-tag circumvent-blocks Overrule blocks but do not affect other actions
client-specific-tag disable-content-filters Disable content-filters but do not affect other actions
+ client-specific-tag overrule-redirects Overrule redirect sections
+ client-specific-tag allow-cookies Do not crunch cookies in either direction
+ client-specific-tag change-tor-socks-port Change forward-socks5 settings to use a different Tor socks port (and circuits)
+ client-specific-tag no-https-inspection Disable HTTPS inspection
+ client-specific-tag no-tls-verification Don't verify certificates when http-inspection is enabled
</screen>
</listitem>
</varlistentry>
<varlistentry>
<term>Notes:</term>
<listitem>
- <warning>
- <para>
- This is an experimental feature. The syntax is likely to change
- in future versions.
- </para>
- </warning>
<para>
In case of some tags users may not want to enable them permanently,
but only for a short amount of time, for example to circumvent a block
<varlistentry>
<term>Notes:</term>
<listitem>
- <warning>
- <para>
- This is an experimental feature. The syntax is likely to change
- in future versions.
- </para>
- </warning>
<para>
If clients reach Privoxy through another proxy, for example a load
balancer, Privoxy can't tell the client's IP address from the connection.
<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.
If you aren't sure if your version supports it, have a look at
The <ulink url="#CA-CERT-FILE">ca-cert-file section</ulink> contains
a command to generate it.
</para>
+ <para>
+ The CA key is used by &my-app; to sign generated certificates.
+ </para>
+ <para>
+ Access to the key should be limited to Privoxy.
+ </para>
</listitem>
</varlistentry>
<varlistentry>