<pre class=
"PROGRAMLISTING"> 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
whenever the IP address is assigned to the system</p>
<p>IPv6 addresses containing colons have to be quoted by brackets. They can only be used if <span class=
"APPLICATION">Privoxy</span> has been compiled with IPv6 support. If you aren't sure if your version
- supports it, have a look at <tt class="LITERAL">http://config.privoxy.org/show-status</tt>.</p>
+ supports it, have a look at <a href="http://config.privoxy.org/show-status" target=
+ "_top">http://config.privoxy.org/show-status</a>.</p>
<p>Some operating systems will prefer IPv6 to IPv4 addresses even if the system has no IPv6 connectivity
which is usually not expected by the user. Some even rely on DNS to resolve localhost which mean the
"localhost" address used may not actually be local.</p>
headers will be emitted in the order given, headers whose name isn't explicitly specified are added at
the end.</p>
<p>Note that sorting headers in an uncommon way will make fingerprinting actually easier. Encrypted
- headers are not affected by this directive.</p>
+ headers are not affected by this directive unless <tt class="LITERAL"><a href=
+ "actions-file.html#HTTPS-INSPECTION" target="_top">https-inspection</a></tt> is enabled.</p>
</dd>
</dl>
</div>
</dd>
<dt>Notes:</dt>
<dd>
- <div class="WARNING">
- <table class="WARNING" border="1" width="90%">
- <tr>
- <td align="center"><b>Warning</b></td>
- </tr>
- <tr>
- <td align="left">
- <p>This is an experimental feature. The syntax is likely to change in future versions.</p>
- </td>
- </tr>
- </table>
- </div>
<p>Client-specific tags allow Privoxy admins to create different profiles and let the users chose which
one they want without impacting other users.</p>
<p>One use case is allowing users to circumvent certain blocks without having to allow them to circumvent
<p>Clients can request tags to be set by using the CGI interface <a href=
"http://config.privoxy.org/client-tags" target="_top">http://config.privoxy.org/client-tags</a>. 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.</p>
+ understands the effect of the tag.</p>
</dd>
<dt>Examples:</dt>
<dd>
<pre class="SCREEN"> # Define a couple of tags, the described effect requires action sections
# 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</pre>
+ 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</pre>
</td>
</tr>
</table>
</dd>
<dt>Notes:</dt>
<dd>
- <div class="WARNING">
- <table class="WARNING" border="1" width="90%">
- <tr>
- <td align="center"><b>Warning</b></td>
- </tr>
- <tr>
- <td align="left">
- <p>This is an experimental feature. The syntax is likely to change in future versions.</p>
- </td>
- </tr>
- </table>
- </div>
<p>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 that is the result of an overly-broad URL pattern.</p>
<p>The CGI interface <a href="http://config.privoxy.org/client-tags" target=
</dd>
<dt>Notes:</dt>
<dd>
- <div class="WARNING">
- <table class="WARNING" border="1" width="90%">
- <tr>
- <td align="center"><b>Warning</b></td>
- </tr>
- <tr>
- <td align="left">
- <p>This is an experimental feature. The syntax is likely to change in future versions.</p>
- </td>
- </tr>
- </table>
- </div>
<p>If clients reach Privoxy through another proxy, for example a load balancer, Privoxy can't tell the
client's IP address from the connection. If multiple clients use the same proxy, they will share the same
client tag settings which is usually not desired.</p>
<div class="SECT2">
<h2 class="SECT2"><a name="HTTPS-INSPECTION-DIRECTIVES" id="HTTPS-INSPECTION-DIRECTIVES">7.7. HTTPS Inspection
(Experimental)</a></h2>
- <p>HTTPS inspection allows to filter encrypted requests. This is only supported when <span class=
- "APPLICATION">Privoxy</span> has been built with FEATURE_HTTPS_INSPECTION.</p>
+ <p>HTTPS inspection allows to filter encrypted requests and responses. This is only supported when <span class=
+ "APPLICATION">Privoxy</span> has been built with FEATURE_HTTPS_INSPECTION. If you aren't sure if your version
+ supports it, have a look at <a href="http://config.privoxy.org/show-status" target=
+ "_top">http://config.privoxy.org/show-status</a>.</p>
<div class="SECT3">
<h4 class="SECT3"><a name="CA-DIRECTORY" id="CA-DIRECTORY">7.7.1. ca-directory</a></h4>
<div class="VARIABLELIST">
<dd>
<p>This directive specifies the name of the CA key file in ".pem" format. The <a href="#CA-CERT-FILE"
target="_top">ca-cert-file section</a> contains a command to generate it.</p>
+ <p>Access to the key should be limited to Privoxy.</p>
</dd>
<dt>Example:</dt>
<dd>
<dd>
<p>This directive specifies the trusted CAs file that is used when validating certificates for
intercepted TLS/SSL requests.</p>
- <p>An example file can be downloaded from <a href="https://curl.haxx.se/ca/cacert.pem" target=
- "_top">https://curl.haxx.se/ca/cacert.pem</a>.</p>
+ <p>An example file can be downloaded from <a href="https://curl.se/ca/cacert.pem" target=
+ "_top">https://curl.se/ca/cacert.pem</a>. If you want to create the file yourself, please see: <a href=
+ "https://curl.se/docs/caextract.html" target="_top">https://curl.se/docs/caextract.html</a>.</p>
</dd>
<dt>Example:</dt>
<dd>
projects / privoxy.git / blobdiff