Rebuild documentation for enable-proxy-authentication-forwarding
[privoxy.git] / doc / webserver / user-manual / config.html
index bff2330..38f75fd 100644 (file)
           </dl>
         </div>
       </div>
+
+      <div class="SECT3">
+        <h4 class="SECT3"><a name="ENABLE-PROXY-AUTHENTICATION-FORWARDING"
+        id="ENABLE-PROXY-AUTHENTICATION-FORWARDING">7.4.9.
+        enable-proxy-authentication-forwarding</a></h4>
+
+        <div class="VARIABLELIST">
+          <dl>
+            <dt>Specifies:</dt>
+
+            <dd>
+              <p>Whether or not proxy authentication through <span class=
+              "APPLICATION">Privoxy</span> should work.</p>
+            </dd>
+
+            <dt>Type of value:</dt>
+
+            <dd>
+              <p>0 or 1</p>
+            </dd>
+
+            <dt>Default value:</dt>
+
+            <dd>
+              <p>0</p>
+            </dd>
+
+            <dt>Effect if unset:</dt>
+
+            <dd>
+              <p>Proxy authentication headers are removed.</p>
+            </dd>
+
+            <dt>Notes:</dt>
+
+            <dd>
+              <p>Privoxy itself does not support proxy authentication, but
+              can allow clients to authenticate against Privoxy's parent
+              proxy.</p>
+
+              <p>By default Privoxy (3.0.21 and later) don't do that and
+              remove Proxy-Authorization headers in requests and
+              Proxy-Authenticate headers in responses to make it harder for
+              malicious sites to trick inexperienced users into providing
+              login information.</p>
+
+              <p>If this option is enabled the headers are forwarded.</p>
+
+              <p>Enabling this option is <span class="emphasis"><i class=
+              "EMPHASIS">not recommended</i></span> if there is no parent
+              proxy that requires authentication or if the local network
+              between Privoxy and the parent proxy isn't trustworthy. If
+              proxy authentication is only required for some requests, it is
+              recommended to use a client header filter to remove the
+              authentication headers for requests where they aren't
+              needed.</p>
+            </dd>
+          </dl>
+        </div>
+      </div>
     </div>
 
     <div class="SECT2">