From: Fabian Keil <fk@fabiankeil.de> Date: Mon, 26 Jun 2017 12:16:32 +0000 (+0000) Subject: Document the enable-accept-filter directive X-Git-Tag: v_3_0_27~107 X-Git-Url: http://www.privoxy.org/gitweb/%22https:/faq/@default-cgi@/developer-manual/static/@default-cgi@send-stylesheet?a=commitdiff_plain;h=65e01393b77af2ab94844cb13efb3d5e321f1254;p=privoxy.git Document the enable-accept-filter directive Sponsored by: Robert Klemme --- diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index 978f93e7..d509c42f 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3,7 +3,7 @@ Purpose : Used with other docs and files only. - $Id: p-config.sgml,v 2.126 2017/05/29 10:02:37 fabiankeil Exp $ + $Id: p-config.sgml,v 2.127 2017/06/26 12:14:38 fabiankeil Exp $ Copyright (C) 2001-2017 Privoxy Developers https://www.privoxy.org/ See LICENSE. @@ -97,7 +97,7 @@ Sample Configuration File for Privoxy &p-version; </title> <para> - $Id: p-config.sgml,v 2.126 2017/05/29 10:02:37 fabiankeil Exp $ + $Id: p-config.sgml,v 2.127 2017/06/26 12:14:38 fabiankeil Exp $ </para> <para> Copyright (C) 2001-2017 Privoxy Developers https://www.privoxy.org/ @@ -3255,6 +3255,77 @@ forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title> </sect3> +<sect3 renderas="sect4" id="enable-accept-filter"><title>enable-accept-filter</title> +<variablelist> + <varlistentry> + <term>Specifies:</term> + <listitem> + <para> + Whether or not Privoxy should use an accept filter + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Type of value:</term> + <listitem> + <para> + <replaceable>0 or 1</replaceable> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Default value:</term> + <listitem> + <para>0</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Effect if unset:</term> + <listitem> + <para> + No accept filter is enabled. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Notes:</term> + <listitem> + <para> + Accept filters reduce the number of context switches by not + passing sockets for new connections to Privoxy until a complete + HTTP request is available. + </para> + <para> + As a result, Privoxy can process the whole request right away + without having to wait for additional data first. + </para> + <para> + For this option to work, Privoxy has to be compiled with + FEATURE_ACCEPT_FILTER and the operating system has to support + it (which may require loading a kernel module). + </para> + <para> + Currently accept filters are only supported on FreeBSD-based + systems. Check the + <ulink url="https://www.freebsd.org/cgi/man.cgi?query=accf_http">accf_http(9) + man page</ulink> + to learn how to enable the support in the operating system. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Examples:</term> + <listitem> + <para> + enable-accept-filter 1 + </para> + </listitem> + </varlistentry> +</variablelist> +<![%config-file;[<literallayout>@@#enable-accept-filter 1</literallayout>]]> +</sect3> + + <sect3 renderas="sect4" id="handle-as-empty-doc-returns-ok"><title>handle-as-empty-doc-returns-ok</title> <variablelist> <varlistentry>