Apache 2.0.14 Released as Alpha Page 2

http://www.netcraft.co.uk/Survey/) found that more web servers were
using Apache than any other software running on more than 60% of the
Internet web servers.

For more information, please check out http://www.apache.org/httpd.html

Known problems with Apache 2.0.14

  *) WARNING: Apache 2.0b1 is not expected to run on Windows 95, 98 or ME.
     The intitial production release of Apache 2.0 is expected to run on
     these consumer operating systems, but they cannot be recommended as
     production environments due to the lack of integrated security and
     robustness.

  *) The canonical paths are being overhauled.  This affects especially
     Win32 users with this release.  Due to this transitional state,
     file with names containing non-ASCII characters may refuse serve.
     This is in preparation for the next release, users will be able to
     serve any Unicode named files with Apache/Win32 on Windows NT/2000.

  *) Win32 users will see no message when Apache 2.0b1 is started as a
     console.  While normal for unix, this differs from the behavior in
     Apache 1.3 on Windows.

Changes with Apache 2.0.14

  *) Fix content-length computation.  We ONLY compute a content-length if
     We are not in a 1.1 request and we cannot chunk, and this is a keepalive
     or we already have all the data.  [Ryan Bloom]

  *) Report unbounded containers in the config file.  Previously, a typo
     in the  directive could result in the rest of the config
     file being silently ignored, with undesired defaults used.
     [Jeff Trawick]

  *) Make the old_write filter use the ap_f* functions for the buffering.
     [Ryan Bloom]

  *) Move more code from the http module into the core server.  This
     is core code, basically the default handler, the default input
     and output filters, and all of the core configuration directives.
     All of this code is required in order for the server to work, with or
     without HTTP.  The server is closer to working without the HTTP