httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-docs-1.3/htdocs/manual/misc perf-bsd44.html
Date Mon, 14 Jan 2002 04:55:53 GMT
fanf        02/01/13 20:55:53

  Modified:    htdocs/manual/misc perf-bsd44.html
  Remove obsolete mumbo-jumbo about HTTP/0.9 compatibility.
  Revision  Changes    Path
  1.20      +8 -29     httpd-docs-1.3/htdocs/manual/misc/perf-bsd44.html
  Index: perf-bsd44.html
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/perf-bsd44.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- perf-bsd44.html	16 Dec 2001 06:30:25 -0000	1.19
  +++ perf-bsd44.html	14 Jan 2002 04:55:53 -0000	1.20
  @@ -232,15 +232,6 @@
       already available to be read) so there is less context
  -    <p>There are two filters in FreeBSD at the time of writing:
  -    "dataready" and "httpready". The former just waits for the
  -    first packet to arrive from the client; the latter waits for
  -    the end of the HTTP headers. Unfortunately the "httpready"
  -    filter breaks support for HTTP/0.9 (which doesn't have headers)
  -    so Apache doesn't use it, but the "dataready" filter gives the
  -    same benefit in the majority of cases so Apache attempts to use
  -    that instead.</p>
       <p>Accept filters provide the most benefit on servers that are
       already so busy that they are configured with "<code>KeepAlive
       Off</code>". <a href="../keepalive.html">HTTP KeepAlive (aka
  @@ -256,32 +247,20 @@
       <p>To enable accept filtering, you must either load the
       appropriate accept filter module, e.g. with the command
  -    <code>kldload accf_data</code>, or compile a kernel with
  -    <code>options ACCEPT_FILTER_DATA</code>. Apache will then
  +    <code>kldload accf_http</code>, or compile a kernel with
  +    <code>options ACCEPT_FILTER_HTTP</code>. Apache will then
       enable filtering when it is restarted.</p>
  -    <p>Accept filters ar compiled in if the symbol
  -    <code>SO_ACCEPTFILTER</code> is defined on the machine apache
  -    is build.</p>
  -    <p>Additionally there is a directive <a
  +    <p>Accept filters are compiled in if the symbol
  +    <code>SO_ACCEPTFILTER</code> is defined on the machine on which
  +    Apache is built. Additionally there is a directive <a
       href="../mod/core.html#acceptfilter">AcceptFilter</a> to switch
       the filters on or off. The default is on; except when apache is
       compiled with <code>-D AP_ACCEPTFILTER_ON</code>.</p>
  -    <p>If you are more concerned about performance than
  -    compatibility with absurdly obsolete HTTP/0.9 user agents then
  -    you can recompile Apache to use the "httpready" filter. This
  -    may be particularly helpful if your web site uses really big
  -    cookies, for example. If you are using
  -    <code>src/Configure</code> then add
  -    <code>-DACCEPT_FILTER_NAME=\"httpready\"</code> to the
  -    <code>EXTRA_CFLAGS</code> line in the
  -    <code>src/Configuration</code> file. If you are using APACI
  -    (aka <code>./configure</code>) then use the command
  -    <code>CFLAGS=-DACCEPT_FILTER_NAME=\'\"httpready\"\'
  -    ./configure</code> (with all the funky backslashed quotes).</p>
  -    <hr />
  +    <p>See the manual page
  +    <a href="">accf_http(9)</a>
  +    for more information.</p>
       <h3>More welcome!</h3>
       If you have tips to contribute, send mail to <a

View raw message