Update to reflect the release.

[apache] / STATUS

APACHE 2.0 STATUS:                                              -*-text-*-
Last modified at [$Date: 2002/05/06 22:14:09 $]

Release:

    2.0.37  : in development.
    2.0.36  : released May 6, 2002 as GA.
    2.0.35  : released April 5, 2002 as GA.
    2.0.34  : tagged March 26, 2002.
    2.0.33  : tagged March 6, 2002.  not released.
    2.0.32  : released Feburary 16, 2002 as beta.
    2.0.31  : rolled Feburary 1, 2002.  not released.
    2.0.30  : tagged January 8, 2002.  not rolled.
    2.0.29  : tagged November 27, 2001.  not rolled.
    2.0.28  : released November 13, 2001 as beta.
    2.0.27  : rolled November 6, 2001
    2.0.26  : tagged October 16, 2001.  not rolled.
    2.0.25  : rolled August 29, 2001
    2.0.24  : rolled August 18, 2001
    2.0.23  : rolled August 9, 2001
    2.0.22  : rolled July 29, 2001
    2.0.21  : rolled July 20, 2001
    2.0.20  : rolled July 8, 2001
    2.0.19  : rolled June 27, 2001
    2.0.18  : rolled May 18, 2001
    2.0.17  : rolled April 17, 2001
    2.0.16  : rolled April 4, 2001
    2.0.15  : rolled March 21, 2001
    2.0.14  : rolled March 7, 2001
    2.0a9   : released December 12, 2000
    2.0a8   : released November 20, 2000
    2.0a7   : released October 8, 2000
    2.0a6   : released August 18, 2000
    2.0a5   : released August 4, 2000
    2.0a4   : released June 7, 2000
    2.0a3   : released April 28, 2000
    2.0a2   : released March 31, 2000
    2.0a1   : released March 10, 2000

Please consult the following STATUS files for information
on related projects:

    * srclib/apr/STATUS
    * srclib/apr-util/STATUS
    * docs/STATUS


CURRENT RELEASE NOTES:

    * 36 status: released on Monday, May 6, 2002.
                 Awaiting the .zip files to complete the release.

RELEASE SHOWSTOPPERS:

    * for 2.0.37: decide if the MMN bump was warranted

    * Move mod_deflate out of experimental

CURRENT VOTES:

    * Should we always build [support*] binaries statically unless otherwise
      indicated?
        Message-ID: <20020129210006.B23512@Lithium.MeepZor.Com>

      +1:  Ken, *wrowe [they are PITAs on OSX]
      -1:  Justin, Ian
        
    * If the parent process dies, should the remaining child processes
      "gracefully" self-terminate. Or maybe we should make it a runtime
      option, or have a concept of 2 parent processes (one being a 
      "hot spare").
      See: Message-ID: <3C58232C.FE91F19F@Golux.Com>

      Self-destruct: Ken, Martin
      Not self-destruct: BrianP, Ian, Cliff, BillS
      Make it runtime configurable: Aaron, Jim, Justin
      Have 2 parents: +1: Jim
                      -1: Justin, wrowe [for 2.0]
                      +0: Martin (while standing by, could it do
                                  something useful?)

    * Make the worker MPM the default MPM for threaded Unix boxes.
      +1:   Justin, Ian, Cliff, BillS
      +0:   BrianP (mutex contention is looking better with the
            latest code, let's continue tuning and testing)
      -0:   Lars
      -1:   Aaron (premature decision, needs more discussion and bug fixes)

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
    * Get mod_cache/mod_mem_cache out of experimental (still some
      work items left to complete)

    * The 2.0.36 worker MPM graceless shutdown changes work but are
      a bit clunky on some platforms; eg, on Linux, the loop to
      join each worker thread seems to hang, and the parent ends up
      killing off the child with SIGKILL.  But at least it shuts down.

    * --enable-mods-shared="foo1 foo2" is busted on Darwin.  Pier
        posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).

    * We do not properly substitute the prefix-variables in the configuration
      scripts or generated-configs.  (i.e. if sysconfdir is etc,
      httpd-std.conf points to conf.)

    * If any request gets through ap_process_request_internal() and is
      scheduled to be served by the core handler, without a flag that this 
      r->filename was tested by dir/file_walk, we need to 500 at the very 
      end of the ap_process_request_internal() processing so sub_req-esters
      know this request cannot be run.  This provides authors of older 
      modules better compatibility, while still improving the security and 
      robustness of 2.0. 

        Status: still need to decide where this goes, OtherBill comments...
        Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
        [Deleted comments regarding the ap_run_handler phase, as irrelevant
            as BillS points out that "common case will be caught in
            default_handler already (with the r->finfo.filetype == 0 check)"
            and the issue is detecting this -before- we try to run the req.]

        gregames says: can this happen somehow without a broken module
            being involved?  If not, why waste cycles trying to defend against
            potential broken modules?  It seems futile.
        wrowe counters: no, it shouldn't happen unless the module is broken.
            But the right answer is to fail the request up-front in dir/file
            walk if the path was entirely invalid; and we can't do that either
            or we break modules that are unwilling to hook map_to_storage.

    * Rewrite core_output_filter. It is nearly impossible to support
      it with predictable results as it is implemented now.

    * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me
      how the Perchild MPM should be re-written.  It hasn't worked
      correctly since filters were added because it wasn't possible to
      get the content that had already been written and the socket at
      the same time.  This mode lets us do that, so the MPM can be
      fixed.

    * htpasswd blindly processes the file you give it, and does no
      sanity checking before totally corrupting whatever file it was
      you thought you had. It should check the input file and bail
      if it finds non-comment lines that do not contain exactly 1
      ':' character.
        Message-ID: <20020217150457.A31632@clove.org>

    * Can a static httpd be built reliably?
        Message-ID: <20020207142751.T31582@clove.org>

    * [Ken] Test suite failures:
      o worker is also failing some of the 'cgi' subtests
      (see <URL:http://Source-Zone.Org/Apache/regression/>):
        Justin says: "Worker should be fine and passes httpd-test here.
                      If you can provide evidence that it can be reproduced
                      outside of httpd-test, then it's a showstopper.  I
                      think it's a perl or a httpd-test problem."
        Not a showstopper: Justin

    * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
      removed if possible.
        Message-ID: <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
        
    * There is a bug in how we sort some hooks, at least the pre-config
      hook.  The first time we call the hooks, they are in the correct 
      order, but the second time, we don't sort them correctly.  Currently,
      the modules/http/config.m4 file has been renamed to 
      modules/http/config2.m4 to work around this problem, it should moved
      back when this is fixed.    rbb
        Justin says: "Is this really a showstopper?  This has been here
                      forever.  What's wrong?  Does this have to do with
                      autoconf or m4?"
        Not a showstopper: Justin, BrianP, trawick, gregames

    * The Add...Filter and Set...Filter directives do not allow the
      administrator to order filters, beyond the order of filename (mime)
      extensions.  It isn't clear if Set...Filter(s) should be inserted 
      before or after the Add...Filter(s) which are ordered by sequence of
      filename extensions.  At minimum, some sort of +-[0-10] syntax seems
      like the quickest fix for a 2.0 gold release.
        Justin says: "Could we delay this for a point release or 2.1?"
        Not a showstopper: justin, wrowe, trawick, stoddard, Jim, Ian, Aaron,
                           gregames

    * Get perchild to work on platforms other than Linux. This
      will require a portable mechanism to pass data and file/socket
      descriptors between vhost child groups. An API was proposed
      on dev@apr:
        Message-ID: <20020111115006.K1529@clove.org>

    * Try to get libtool inter-library dependency code working on AIX.
        Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>

      Justin says: If we get it working on AIX, we can enable this
                   on all platforms and clean up our build system
                   somewhat.
      Jeff says:   I thought I tested a patch for you sometime in
                   January that you were going to commit within a few
                   days.

    * Handling of %2f in URIs.  Currently both 1.3 and 2.0
      completely disallow %2f in the request URI path (see
      ap_unescape_url() in util.c).  It's permitted and passed
      through in the query string, however.  Roy says the
      original reason for disallowing it, from five years ago,
      was to protect CGI scripts that applied PATH_INFO to
      a filesystem location and which might be tricked by
      ..%2f..%2f(...).  We *should* allow path-info of the
      form 'http://foo.com/index.cgi/path/to/path%2finfo'.
      Since we've revamped a lot of our processing of path
      segments, it would be nice to allow this, or at least
      allow it conditionally with a directive.

    * FreeBSD, threads, and worker MPM.  All seems to work fine 
      if you only have one worker process with many threads.  Add 
      a second worker process and the accept lock seems to be
      lost.  This might be an APR issue with how it deals with
      the child_init hook (i.e. the fcntl lock needs to be resynced).
      More examination and analysis is required.
        Status: This has also been reported on Cygwin.  
        Message-ID: <3C2CC514.8EF3BED1@wapme-systems.de> (cygnus)

      Justin says: So, FreeBSD-CURRENT and Cywin have the same 
                   problem.  Yum.  If another platform has this
                   with worker, this becomes a showstopper.
      Aaron says: I spent some time disecting this and have come to
              the conclusion that it is not a problem in the worker MPM
              (or at least, it is not isolated to a problem in worker).
              I'll list some of the problems I'm seeing in case someone
              else wants to pick up where I've left off:
               - Delivery of just about any signal to one of the child
                 processes will send it into an infinite loop as well.
               - Even though the parent is spinning out of control,
                 at first the child or children will appear to work
                 properly. At times it is possible to get it into a state,
                 however, where a request will hang until another concurrent
                 request "kicks" the first, at which point the second will
                 hang. My theory is that this has to do with the
                 pthread_cond_*() implementation in FreeBSD, but it's still
                 possible that it is in APR.
      
      Justin adds: Oh, FreeBSD threads are implemented entirely with 
                   select()/poll()/longjmp().  Welcome to the nightmare.
                   So, that means a ktrace output also has the thread 
                   scheduling internals in it (since it is all the same to 
                   the kernel).  Which makes it hard to distinguish between 
                   our select() calls and their select() calls.  
                   *bangs head on wall repeatedly*  But, some of the libc_r 
                   files have a DBG_MSG #define.  This is moderately helpful
                   when used with -DNO_DETACH.  The kernel scheduler isn't 
                   waking up the threads on a select().  Yum.  And, I bet 
                   those decrementing select calls have to do with the 
                   scheduler.  Time to brush up on our OS fundamentals.

    * There is increasing demand from module writers for an API
      that will allow them to control the server à la apachectl.
      Reasons include sole-function servers that need to die if
      an external dependency (e.g., a database) fails, et cetera.
      Perhaps something in the (ever more abused) scoreboard?
        rbb: I don't believe the scoreboard is the correct mechanism
             for this.  We already have a pipe that goes between parent
             and child for graceful shutdown events, along with an API that
             can be used to send a message down that pipe.  In threaded MPMs,
             it is easy enough to make that one pipe be used for graceful
             and graceless events, and it is also easy to open that pipe
             to both parent and child for writing.  Then we just need to
             figure out how to do graceless on non-threaded MPMs.

    * Allow the DocumentRoot directive within <Location > scopes?  This
      allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
      by a <Directory /somepath/foo> to become simply 
      <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more legible
      and in-your-face.)  DocumentRoot unset would be accepted [and would
      not permit content to be served, only virtual resources such as
      server-info or server-status.
        This proposed change would _not_ depricate Alias.

    * Win32: Rotatelogs sometimes is not terminated when Apache
      goes down hard.  FirstBill was looking at possibly tracking the 
      child's-child processes in the parent process.
        OtherBill asks, wasn't this fixed? 
        stoddard: Not fixed. Shared scoreboard might offer a good
        way for the parent to keep track of 'other child' processes
        and whack them if the child goes down.
        Other thoughts on walking the process chain using the NT kernel
        have also been proposed on APR.

    * Win32: Add a simple hold console open patch (wait for close or
        the ESC key, with a nice message) if the server died a bad 
        death (non-zero exit code) in console mode.
        Resolution: bring forward same ugly hacks from 1.3.13-.20

    * Port of mod_ssl to Apache 2.0:

      The current porting state is summarized in modules/ssl/README. The
      remaining work includes:
      (1) stablizing/optimizing the SSL filter logic
      (2) Enabling SSL extentions
      (3) Trying to seperate the https filter logic from mod_ssl -
          This is to facilitate other modules that wish to use the https
          filter or the mod_ssl logic or both as required.

    * Eliminate unnecessary creation of pipes in mod_cgid

    * Combine log_child and piped_log_spawn. Clean up http_log.c.
      Common logging API.

    * Document mod_file_cache.

    * Platforms that do not support fork (primarily Win32 and AS/400)
      Architect start-up code that avoids initializing all the modules 
      in the parent process on platforms that do not support fork.

    * Win32: Migrate the MPM over to use APR thread/process calls. This
      would eliminate some code in the Win32 branch that essentially
      duplicates what is in APR.

    * There are still a number of places in the code where we are
      losing error status (i.e. throwing away the error returned by a
      system call and replacing it with a generic error code)

    * Mass vhosting version of suEXEC.

    * All DBMs suffer from confusion in support/dbmmanage (perl script) since 
      the dbmmanage employs the first-matched dbm format.  This is not
      necessarily the library that Apache was built with.  Aught to
      rewrite dbmmanage upon installation to bin/ with the proper library 
      for predictable mod_auth_dbm administration.
        Questions; htdbm exists, time to kill dbmmanage, or does it remain
                   useful as a perl dbm management example?  If we keep it,
                   do we address the issue above?

    * Integrate mod_dav.
        Some additional items remaining:
        - case_preserved_filename stuff
            (use the new canonical name stuff?)
        - find a new home for ap_text(_header)
        - is it possible to remove the DAV: namespace stuff from util_xml?

    * ap_core_translate() and its use by mod_mmap_static and mod_file_cache
      are a bit wonky.  The function should probably be exposed as a utility 
      function (such as ap_translate_url2fs() or ap_validate_fs_url() or 
      something).  Another approach would be a new hook phase after
      "translate" which would allow the module to munge what the
      translation has decided to do.
        Status: Greg +1 (volunteers), Ryan +1

    * Explore use of a post-config hook for the code in http_main.c which
      calls ap_fixup_virutal_hosts(), ap_fini_vhost_config(), and
      ap_sort_hooks()  [to reduce the logic in main()]

    * read the config tree just once, and process N times (as necessary)

    * (possibly) use UUIDs in mod_unique_id and/or mod_usertrack

    * (possibly) port the bug fix for PR 6942 (segv when LoadModule is put
      into a VirtualHost container) to 2.0.

    * shift stuff to mod_core.h

    * callers of ap_run_create_request() should check the return value
      for failure (Doug volunteers)

    * Win32: Get Apache working on Windows 95/98. The following work
        (at least) needs to be done:
        - Document warning that OSR2 is required (for Crypt functions, in
        rand.c, at least.)  This could be resolved with an SSL library, or
        randomization in APR itself.
        - Bring the Win9xConHook.dll from 1.3 into 2.0 (no sense till it
        actually works) and add in a splash of Win9x service code.

    * In order to use a DSO version of mod_ssl we have to link with
      -lssl and -lcrypto. A workaround is in place right now where the
      entire EXTRA_LIBS macro is being appended to the objects list, but
      this is a hack. We should either revamp the APACHE_CHECK_SSL_TOOLKIT
      autoconf function or come up with some other autoconf checks to
      search for libssl and libcrypto and properly add them to mod_ssl's
      link flags.

    * Fix the worker MPM to use POD to kill child processes instead
      of ap_os_killpg, regardless of how they should die. (Ryan Bloom)

    * Scoreboard structures could be changed in the future such that
      proper alignment is not maintained, leading to segfaults on 
      some systems.  Cliff posted a patch to deal with this issue but
      later recanted. See this message to dev@apr.apache.org:
      Message-ID: <Pine.LNX.4.44.0203011354090.16457-200000@deepthought
                  .cs.virginia.edu>

EXPERIMENTAL MODULES:
    Experimental modules should eventually be be promoted to fully supported
    status or removed from the repository entirely (ie, the
    'experiment' failed). This section tracks what needs to happen to 
    get the modules promoted to fully supported status.

    mod_cache/mod_mem_cache/mod_disk_cache:
    * mod_cache: handle cache_control: no_cache "field_name" to enable 
      cacheing the response w/o header "field_name"
      See RFC2616 section 14.9.1

    * mod_cache: CacheEnable/CacheDisable should accept regular expressions.

    * mod_cache: Fix dependency on ATOMIC operators. Need
      APR_HAS_ATOMIC_* feature macros.

    * mod_disk_cache: Implement garbage collection

    * mod_mem_cache/mod_disk_cache: Need to be able to query cache
      status (num of entries, cache object properties, etc.).
      mod_status could be extended to query optional hooks defined
      by modules for the purpose of reporting module status.
      mod_cache (et. al.) could define optional hooks that are called
      to collect status.  Status should be queryable by
      HTTP or SNMP?

    * mod_mem_cache: garbage collection. One strategy is to simply
      remove stale entries as we attempt to serve them. Another
      strategy is to kick off a GC thread that traverses the cache
      and preemptively remove stale entries.  How to manage a 
      cache that is full? Do LRU GC? Other? Bueller?

    * mod_mem_cache/mod_disk_cache: Complete implementing config
      directives. 

    * Sample config for mod_cache/mod_mem_cache/mod_disk_cache for
      inclusion into httpd.conf.

    * mod_cache/mod_mem_cache/mod_disk_cache: Documentation.

PRs that have been suspended forever waiting for someone to
put them into 'the next release':

    * PR#76: general
      missing call to "setlocale();"
        Status: 

    * PR#78: mod_include
      Additional status for XBitHack directive
        Status: 

    * PR#362: mod_proxy
      Mod_proxy doesn't allow change of error pages
        Status: 

    * PR#370: mod_env
      Modified PATH environemnt variable is not passed, instead
      system's is used
        Status: 

    * PR#440: mod_proxy
      Proxy doesn't deliver documents if not connected
        Status: 

    * PR#534: mod_proxy
      proxy converts ~name to %7Ename when name starts with a dot (.)
        Status: 

    * PR#537: mod_access
      mod_access syntax allows hosts that should be restricted
        Status: 

    * PR#557: mod_auth-any
      ~UserHome directories are not honored in absolute pathname
      requests (.htaccess)
        Status: 

    * PR#612: mod_proxy
      Proxy FTP Authentication Fails
        Status: 

    * PR#623: mod_include
      A smarter "Last Modified" value for SSI documents (see PR number 600)
        Status: 

    * PR#628: config
      Request of "Options SymLinksIfGroupMatch"
        Status: 

    * PR#700: mod_proxy
      Proxy doesn't do links right for OpenVMS files through ftp:
        Status: 

    * PR#759: mod_imap
      imap should read <MAP><AREA>*</MAP> too!
        Status: 

    * PR#793: general
      RLimitCPU and RLimitMEM don't apply to all children like they should
        Status: 

    * PR#921: suexec
      Uses cwd before filling it in, doesn't use syslog
        Status: 

    * PR#922: config
      it is useful to allow specifiction that root-owned symlinks
      should always be followed
        Status: 

    * PR#980: mod_proxy
      Controlling Access to Remote Proxies would be nice...
        Status: 

    * PR#994: mod_proxy
      Adding authentication "on the fly" through the proxy module
        Status: 

    * PR#1004: apache-api
      request_config field in request_rec is moderately bogus
        Status: 

    * PR#1028: other
      DoS attacks involving memory consumption
        Status: 

    * PR#1050: mod_log-any
      Logging of virtual server to error_log as well
        Status: 

    * PR#1085: mod_proxy
      ProxyRemote make a dead cycle.
        Status: 

    * PR#1117: mod_auth-any
      Using NIS passwd.byname dbm files with AuthDBMUserFile
        Status: 

    * PR#1120: suexec
      suexec does not parse arguments to #exec cmd
        Status: 

    * PR#1145: mod_include
      Allow for Last-Modified: without resorting to XBitHack
        Status: 

    * PR#1158: apache-api
      improvements to child spawning API
        Status: 

    * PR#1166: mod_proxy
      ``nph-'' not honored (no buffering) for ProxyRemote mapping
        Status: 

    * PR#1176: mod_cgi
      Apache cannot handle continuation line in headers
        Status: 

    * PR#1191: general
      setlogin() is not called, causing problems with e.g. identd
        Status: 

    * PR#1204: general
      regerror() exists, use it
        Status: 

    * PR#1233: apache-api
      there is no way to keep per-connection per-module state
        Status: 

    * PR#1263: mod_autoexec
      Add frame-safe anchor attribute to mod_autoindex links
        Status: 

    * PR#1268: suexec
      CGI scripts running as Apache user: security (suexec etc.)
        Status: 

    * PR#1285: suexec
      Error messages could be easier to spot in cgi.log file for suexec.c
        Status: 

    * PR#1287: mod_access
      add allow,deny/deny,allow warning to mod_access
        Status: 

    * PR#1290: mod_proxy
      Need to know "hit-rate" on proxy cache
        Status: 

    * PR#1358: mod_log-any
      Selective url-encode of log fields (or maybe a pseudo
      log_rewrite module?)
        Status: 

    * PR#1383: mod_headers
      I make mod_headers to modify request headers as well as
      response ones.
        Status: 

    * PR#1532: mod_proxy
      Proxy transfer logging
        Status: 

    * PR#1547: mod_proxy
      No HTTP_X_FORWARDED_FOR set...
        Status: 

    * PR#1567: mod_proxy
      ProxyRemote proxy requests fail authentication by firewall
        Status: 

    * PR#1582: mod_rewrite
      mod_rewrite forms REQUEST_URI different than mod_cgi does
        Status: 

    * PR#1677: mod_headers
      mod_headers should allow mod_log_config-style formats in
      header values
        Status: 

    * PR#1702: mod_proxy
      mod_proxy to support persistent conns?
        Status: 

    * PR#1803: mod_include
      patches to mod_include to allow for file tests
        Status: 

    * PR#1809: mod_auth-any
      Suggestion for improving authentication modules and core source
      code, problem with 401 and ErrorDocument
        Status: 

    * PR#1878: mod_proxy
      listing of proxy cache content
        Status: 

    * PR#1905: suexec
      Allow modules to set user:group for execution.
        Status: 

    * PR#2024: apache-api
      adding auth_why to conn_rec
        Status: 

    * PR#2073: mod_log-any
      pipelined connections are not logged correctly
        Status: 

    * PR#2074: mod_rewrite
      mod_rewrite doesn't pass Proxy Throughput on internal subrequests
        Status: 

    * PR#2113: config
      HTTP Server Rebuild Line Needs Changing for the better
        Status: 

    * PR#2138: mod_status
      mod_status always displays 256 possible connection slots
        Status: 

    * PR#2221: documentation
      Make online documentation search link back to my installation
        Status: 

    * PR#2284: general
      Can not POST to ErrorDocument - Apache/1.3b6
        Status: 

    * PR#2314: mod_proxy
      patterns in ProxyRemote
        Status: 

    * PR#2343: mod_status
      Status module averages are for entire uptime
        Status: 

    * PR#2360: suexec
      suexec for general access of user content?
        Status: 

    * PR#2396: general
      Proposal for TimeZone directive
        Status: 

    * PR#2415: mod_info
      /server-info doesn't check for the virtual host to list the info
        Status: 

    * PR#2421: config
      problem specifying ndbm library for build ?with autoconfigure
        Status: 

    * PR#2431: general
      A small addition to rotatelogs.c to improve program functionality.
        Status: 

    * PR#2446: config
      AllowOverride FileInfo is too coarse
        Status: 

    * PR#2460: mod_cgi
      TimeOut applies to output of CGI scripts
        Status: 

    * PR#2512: mod_access
      &lt;IfDenied&gt; directive wanted
        Status: 

    * PR#2573: suexec
      CGI's for general use still have to be run as another user
      with suExec
        Status: 

    * PR#2648: general
      Cache file names in Proxy module
        Status: 

    * PR#2760: config
      [PATCH] User/Group for <Directory> and <Location> i.e. not only
      in global and <Virtual>.
        Status: 

    * PR#2763: general
      mailto tags and bundling bug report script
        Status: 

    * PR#2785: os-aix
      Support for System Resource Controller
        Status: 

    * PR#2793: protocol
      When will Apache support P3P? Any Plans?
        Status: 

    * PR#2873: config
      Feedback/Comment on APACI
        Status: 

    * PR#2889: general
      Inclusion of RPM spec file in CVS/distributions
        Status: 

    * PR#2906: general
      Propose that Apache recommend $UNIQUE_ID for all "session id"
      algorithms
        Status: 

    * PR#2907: config
      suggestion: power up your Include directive :)
        Status: 

    * PR#3018: general
      cannot limit some HTTP methods
        Status: 

    * PR#3143: apache-api
      No module specific data hook for per-connection data
        Status: 

    * PR#3191: mod_negotiation
      no way to set global quality-of-source (qs) coneg values
      with multiviews
        Status: 

    * PR#3568: mod_proxy
      Accessing URL through proxy server corrupts data.
        Status: 

    * PR#3605: mod_proxy
      Some anonymous FTP URLs ask for authentication
        Status: 

    * PR#3677: general
      New ErrorDocumentMatch directive
        Status: 

    * PR#4241: config
      Need to be able to override shebang line to make CGI scripts
      more portable.
        Status: 

    * PR#4244: config
      "Files" and "FilesMatch" regexp does not recognize bang as
      negation operator
        Status: 

    * PR#4448: mod_log-any
      Please allow CGI env variables (QUERY_STRING, ...) to be logged
      with %{}e
        Status: 

    * PR#4459: mod_include
      Suggestion for better handling of Last-modified headers
        Status: 

    * PR#4490: mod_cgi
      mod_cgi prevents handling of OPTIONS requests
        Status: 

    * PR#5713: os-windows
      [PATCH] install as win32 service with domain account
        Status: Cannot accept password-as-arg, we should prompt the
                user when -k install/-k config with a user argument.

    * PR#5993: general
      AllowOverride should have a 'CheckNone' and 'AllowNone' argument
      instead of only 'None'
        Status: 

Other bugs that need fixing:

    * ap_discard_request should be converted to use the bucket API
      directly rather than waste cycles copying buffers with the old API.

    * MaxRequestsPerChild measures connections, not requests.
        Until someone has a better way, we'll probably just rename it
        "MaxConnectionsPerChild".
    
    * Regex containers don't work in an intutive way
        Status: No one has come up with an efficient way to fix this
        behavior. Dean has suggested getting rid of regex containers
        completely.
        OtherBill suggests: We at least seem to agree on eliminating
                            the <Container ~ foo> forms, and using only
                            <ContainerMatch foo> semantics.

    * SIGSEGV on Linux (glibc 2.1.2) isn't caught properly by a
      sigwaiting thread. We need to work around this, perhaps unless
      there is hope soon for a fixed glibc.

    * orig_ct in the byterange/multipart handling may not be
      needed. Apache 1.3 just never stashed "multipart" into
      r->content_type. We should probably follow suit since the
      byterange stuff doesn't want the rest of the code to see the
      multipart content-type; the other code should still think it is
      dealing with the <orig_ct> stuff.
        Status: Greg volunteers to investigate (esp. since he was most 
                likely the one to break it :-)

Binaries (2.0.35):

 Platform                      Avail.  Volunteer
 ------------------------------------------------------------------
 AIX 4.3.3                             Bill Stoddard
 Mandrake 8.1                  no      Ryan Bloom
 FreeBSD 4.1                   yes     Ryan Bloom
 i386-unknown-freebsd4.5       yes     Aaron Bannert
 OS X 10.1.3/Darwin 5.3        yes     Jim Jagielski
 Solaris 8.x/sparc             yes     Jim Jagielski
 i686-pc-linux-gnu-rh70        yes     Aaron Bannert
 i686-pc-linux-gnu-rh72        yes     Aaron Bannert
 i386-pc-solaris2.8            yes     Aaron Bannert
 powerpc-unknown-linux-gnu     yes     Graham Leggett
 NetWare                       yes     Brad Nicholes
 Win32-x86                     yes     William Rowe

Other features that need writing:

    * Finish infrastructure in core for async MPMs
        Status: post 2.0

    * TODO in source -- just do an egrep on "TODO" and see what's there

Available Patches:

   * Martin Sojka <msojka@gmx.de>'s patch to add error reporting for failed 
     htpasswd actions due to a full /tmp volume (other programs may have
     similar problems?)
        PR: 6475
        Status:

   * Mike Abbott's <mja@trudge.engr.sgi.com> patches to improve
     performance
       Status: These were written for 1.3, and are awaiting a port to
       2.0
 
   * Jim Winstead's <jimw@trainedmonkey.com> patch to add CookieDomain and 
     other small mod_usertrack features

   * Dan Rench's <drench@xnet.com> patch to add allow the errmsg and timefmt 
     of SSI's to be modified in the config file.  Patch is available in 
     PR6193

Open issues:

   * Which MPMs will be included with Apache 2.0?