STATUS revision aec9747aa70c1dce98e536e8eef5a6a0ab0f1d6c
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorAPACHE 2.3 STATUS: -*-text-*-
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorLast modified at [$Date$]
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorThe current version of this file can be found at:
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorDocumentation status is maintained seperately and can be found at:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * docs/STATUS in this source tree, or
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorConsult the following STATUS files for information on related projects:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorPatches considered for backport are noted in their branches' STATUS:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorRelease history:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor while x.{even}.z versions are Stable/GA releases.]
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.10 : In development.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.9 : Tagged on November 23, 2010.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.8 : Tagged on August 24, 2010.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.7 : Tagged on August 19, 2010, not released.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.6 : Released on June 21, 2010.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.5 : Released on January 26, 2010.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.4 : Released on December 8, 2009.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.3 : Tagged on November 11, 2009, not released.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.2 : Tagged on March 23, 2009, not released.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 2.3.1 : Tagged on January 2, 2009, not released.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis 2.3.0 : Tagged on December 6, 2008, not released.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentisContributors looking for a mission:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Just do an egrep on "TODO" or "XXX" in the source.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Review the bug database at: http://issues.apache.org/bugzilla/
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Review the "PatchAvailable" bugs in the bug database:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis After testing, you can append a comment saying "Reviewed and tested".
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Open bugs in the bug database.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * See also the STATUS file in the docs/ directory, which lists documentation-specific TODO items.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentisCURRENT RELEASE NOTES:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentisRELEASE SHOWSTOPPERS:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Modules that are not ready for production use should be marked as
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis experimental. Candidates:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis - MPM simple
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Review the example configuration. It should be based on current best
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor practices and not use deprecated features.
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Modules without documentation need to be moved to experimental or be
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Not all MPMs are updated to set conn_rec::current_thread correctly.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor (Prefork, Worker, Event, Simple are updated).
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jim sez: Then we just ship with those... mark any others as
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor experimental
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor FOR NEXT ALPHA:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * The mod_session* modules need to be checked that their hooks respect
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the returning of int (HTTP status codes) and apr_status_t as appropriate,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor and any anomolies fixed.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_ssl's proxy support only allows one proxy client certificate per
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor frontend virtual host. Lift this restriction.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis * Handling of non-trailing / config by non-default handler is broken
4721c0c3564368123b87ba96db0bde5e3dd44357lgentis http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jerenkrantz asks: Why should this block a release?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor wsanchez agrees: this may be a change in behavior, but isn't
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf clearly wrong, and even if so, it doesn't seem like a
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor showstopper.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * the edge connection filter cannot be removed
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jerenkrantz asks: Why should this block a release?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor stas replies: because it requires a rewrite of the filters stack
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor implementation (you have suggested that) and once 2.2 is
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor released you can't do that anymore.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor pgollucci: this affects mod_perl I'm pretty sure.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorCURRENT VOTES:
03fc700cc2a7b22b84891f9595f23e40d5243b62lgentis * Name the Server (version 2.4 or 3.0, depending on the final call)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Recent discussion indicates we should designate a (short name).
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor This is not yet a [Vote] - Your nominations please:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Apache HTTP Server (httpd)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor +1: sctemme (why mess with it?)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Maybe remove Limit/LimitExcept or at least make it log warnings when
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Sort out modules selections for most/all/reallyall. Maybe rename
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor all -> most, reallyall -> all, and remove the old 'most'.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Add mod_define.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Patches submitted to the bug database:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Filter stacks and subrequests, redirects and fast redirects.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor There's at least one PR that suffers from the current unclean behaviour
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor (which lets the server send garbage): PR 17629
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor nd says: Every subrequest should get its own filter stack with the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor subreq_core filter as bottom-most. That filter does two things:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor - swallow EOS buckets
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor - redirect the data stream to the upper request's (rr->main)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor filter chain directly after the subrequest's starting
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Once we have a clean solution, we can try to optimize
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor it, so that the server won't be slow down too much.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * RFC 2616 violations.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Closed PRs: 15852, 15857, 15859, 15861, 15864, 15869, 15870, 16120,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 16125, 16135, 16136, 16137, 16138, 16139, 16140, 16518,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 16520, 42978, 49825
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Open PRs: 15865, 15866, 15868, 16126, 16133, 16142, 16521
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jerenkrantz says: need to decide how many we need to backport and/or
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor if these rise to showstopper status.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor out of this list, without reviewing them individually.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * pipes deadlock on all platforms with limited pipe buffers (e.g. both
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Linux and Win32, as opposed to only Win32 on 1.3). The right solution
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * All handlers should always send content down even if r->header_only
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor is set. If not, it means that the HEAD requests don't generate the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor same headers as a GET which is wrong.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * exec cmd and suexec arg-passing enhancements
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Status: Patches proposed
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis (see the "proc.patch" and "suexec-shell.patch" links in this message)
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis * The 2.0.36 worker MPM graceless shutdown changes work but are
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis a bit clunky on some platforms; eg, on Linux, the loop to
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis join each worker thread seems to hang, and the parent ends up
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis killing off the child with SIGKILL. But at least it shuts down.
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis chrisd: Has this been fixed by the changes for PR 38737?
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis * We do not properly substitute the prefix-variables in the configuration
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis scripts or generated-configs. (i.e. if sysconfdir is etc,
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis httpd-std.conf points to conf.)
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis * If any request gets through ap_process_request_internal() and is
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis scheduled to be served by the core handler, without a flag that this
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis r->filename was tested by dir/file_walk, we need to 500 at the very
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis end of the ap_process_request_internal() processing so sub_req-esters
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis know this request cannot be run. This provides authors of older
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis modules better compatibility, while still improving the security and
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis robustness of 2.0.
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis Status: still need to decide where this goes, OtherBill comments...
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis [Deleted comments regarding the ap_run_handler phase, as irrelevant
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis as BillS points out that "common case will be caught in
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis default_handler already (with the r->finfo.filetype == 0 check)"
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis and the issue is detecting this -before- we try to run the req.]
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor gregames says: can this happen somehow without a broken module
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor being involved? If not, why waste cycles trying to defend against
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor potential broken modules? It seems futile.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor wrowe counters: no, it shouldn't happen unless the module is broken.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor But the right answer is to fail the request up-front in dir/file
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor walk if the path was entirely invalid; and we can't do that either
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Can a static httpd be built reliably?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Message-ID: <20020207142751.T31582@clove.org>
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor removed if possible.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Message-ID:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Jeff wonders if we still care about this. It is no longer an
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor API issue but simply an extra trip through the brigade.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Try to get libtool inter-library dependency code working on AIX.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Justin says: If we get it working on AIX, we can enable this
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor on all platforms and clean up our build system somewhat.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Jeff says: I thought I tested a patch for you sometime in
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor January that you were going to commit within a few days.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Handling of %2f in URIs. Currently both 1.3 and 2.0
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor completely disallow %2f in the request URI path (see
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor ap_unescape_url() in util.c). It's permitted and passed
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor through in the query string, however. Roy says the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor original reason for disallowing it, from five years ago,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor was to protect CGI scripts that applied PATH_INFO to
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor a filesystem location and which might be tricked by
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor ..%2f..%2f(...). We *should* allow path-info of the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Since we've revamped a lot of our processing of path
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor segments, it would be nice to allow this, or at least
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor allow it conditionally with a directive.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor OtherBill adds that %2f as the SECOND character of a multibyte
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor sequence causes the request to fail! This happens notably in
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the ja-jis encoding.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * There is increasing demand from module writers for an API
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor that will allow them to control the server à la apachectl.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Reasons include sole-function servers that need to die if
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor an external dependency (e.g., a database) fails, et cetera.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Perhaps something in the (ever more abused) scoreboard?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor On the other hand, we already have a pipe that goes between parent
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor and child for graceful shutdown events, along with an API that
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor can be used to send a message down that pipe. In threaded MPMs,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor it is easy enough to make that one pipe be used for graceful
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor and graceless events, and it is also easy to open that pipe
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor to both parent and child for writing. Then we just need to
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor figure out how to do graceless on non-threaded MPMs.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Allow the DocumentRoot directive within <Location > scopes? This
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor by a <Directory /somepath/foo> to become simply
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more legible
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor and in-your-face.) DocumentRoot unset would be accepted [and would
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor not permit content to be served, only virtual resources such as
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor server-info or server-status.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor This proposed change would _not_ depricate Alias.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor striker: See the thread starting with Message-ID:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Win32: Rotatelogs sometimes is not terminated when Apache
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor goes down hard. FirstBill was looking at possibly tracking the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor child's-child processes in the parent process.
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf stoddard: Shared scoreboard might offer a good way for the parent
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor to keep track of 'other child' processes and whack them if the child
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Other thoughts on walking the process chain using the NT kernel
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor have also been proposed on APR.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Eliminate unnecessary creation of pipes in mod_cgid
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Combine log_child and piped_log_spawn. Clean up http_log.c.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Common logging API.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Platforms that do not support fork (primarily Win32 and AS/400)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Architect start-up code that avoids initializing all the modules
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor in the parent process on platforms that do not support fork.
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf * There are still a number of places in the code where we are
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor losing error status (i.e. throwing away the error returned by a
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor system call and replacing it with a generic error code)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Mass vhosting version of suEXEC.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * All DBMs suffer from confusion in support/dbmmanage (perl script) since
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the dbmmanage employs the first-matched dbm format. This is not
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor necessarily the library that Apache was built with. Aught to
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor rewrite dbmmanage upon installation to bin/ with the proper library
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor for predictable mod_auth_dbm administration.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Questions; htdbm exists, time to kill dbmmanage, or does it remain
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor useful as a perl dbm management example? If we keep it,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor do we address the issue above?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Integrate mod_dav.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Some additional items remaining:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor - case_preserved_filename stuff
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor (use the new canonical name stuff?)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor - find a new home for ap_text(_header)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor - is it possible to remove the DAV: namespace stuff from util_xml?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * ap_core_translate() and its use by mod_mmap_static and mod_file_cache
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor are a bit wonky. The function should probably be exposed as a utility
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor function (such as ap_translate_url2fs() or ap_validate_fs_url() or
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor something). Another approach would be a new hook phase after
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor "translate" which would allow the module to munge what the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor translation has decided to do.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Status: Greg +1 (volunteers)
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf * Explore use of a post-config hook for the code in http_main.c which
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor calls ap_fixup_virutal_hosts(), ap_fini_vhost_config(), and
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor ap_sort_hooks() [to reduce the logic in main()]
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * read the config tree just once, and process N times (as necessary)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * (possibly) use UUIDs in mod_unique_id and/or mod_usertrack
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * (possibly) port the bug fix for PR 6942 (segv when LoadModule is put
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor into a VirtualHost container) to 2.0.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * shift stuff to mod_core.h
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * callers of ap_run_create_request() should check the return value
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor for failure (Doug volunteers)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Fix the worker MPM to use POD to kill child processes instead
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor of ap_os_killpg, regardless of how they should die.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor chrisd: Is this done, by any chance? See r92598 and r93358.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Scoreboard structures could be changed in the future such that
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor proper alignment is not maintained, leading to segfaults on
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor some systems. Cliff posted a patch to deal with this issue but
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor later recanted. See this message to dev@apr.apache.org:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Message-ID:
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor <Pine.LNX.4.44.0203011354090.16457-200000@deepthought.cs.virginia.edu>
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * APXS either needs to be fixed completely for use when apr is out of tree,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor or it should drop query mode altogether, and we just grow an
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor httpd-config or similar arrangement.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor To quote a discussion in STATUS earlier:
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf thommay: this doesn't fix all the problems with apxs and out of
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor tree apr/apr-util, but it's a good start. There's still the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor query cases; but I'm beginning to think that in these cases
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the app should be querying ap{r,u}-config directly
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor deprecate -q: add htpd-config: gstein, pquerna, minfrin, pgollucci
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorTODO ISSUES REMAINING IN MOD_SSL:
7623d90953885c8fa9e0dbc617ce9953eab30ef9lgentis * Do we need SSL_set_read_ahead()?
7623d90953885c8fa9e0dbc617ce9953eab30ef9lgentis * SSLRequire directive (parsing of) leaks memory
7623d90953885c8fa9e0dbc617ce9953eab30ef9lgentis * Diffie-Hellman-Parameters for temporary keys are hardcoded in
7623d90953885c8fa9e0dbc617ce9953eab30ef9lgentis ssl_engine_dh.c, while the comment in ssl_engine_kernel.c says:
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf "it is suggested that keys be changed daily or every 500
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor transactions, and more often if possible."
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * ssl_var_lookup could be rewritten to be MUCH faster
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * CRL callback should be pluggable
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * session cache store should be pluggable
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * init functions should return status code rather than ssl_die()
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * ssl_engine_pphrase.c needs to be reworked so it is generic enough
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor to also decrypt proxy keys
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * output warning when allowing SSL v2.0 ? its so old
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_proxy: Ability to run SSL over proxy gateway connections,
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor encrypting (or reencrypting) at the proxy.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_cache: Handle ESI tags.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_cache: Resolve issue of how to cache page fragments (or perhaps
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor -if- we want to cache page fragments). Today, mod_cache/mod_mem_cache
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor will cache #include 'virtual' requests (but not #include 'file'
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor requests). This was accomplished by making CACHE_IN a
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor filter. But now responses cannot be cached that include the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor effects of having been run through CONTENT_SET filters
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor (mod_deflate, mod_expires, etc). We could rerun all the
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf CONTENT_SET filters on the cached response, but this will not
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor work in all cases. For example, mod_expires relies on installing
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the EXPIRATION filter during fixups. Contents served out of
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor mod_cache (out of the quick_handler) bypass -all- the request
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor line server hooks (Ryan really hated this. It is great for
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor performance, but bad because of the complications listed above).
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_mem_cache: Consider adding a RevalidateTimeout directive to
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor specify time at which local cached content is to be revalidated
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor (ie, underlying file stat'ed to see if it has changed).
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_cache: CacheEnable/CacheDisable should accept regular expressions.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jerenkrantz says: Too slow. Get regexs away from speedy caches by
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf default. Introduce a new CacheEnableRegex if you want.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * mod_mem_cache/mod_disk_cache: Need to be able to query cache
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor status (num of entries, cache object properties, etc.).
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor mod_status could be extended to query optional hooks defined
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor by modules for the purpose of reporting module status.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor mod_cache (et. al.) could define optional hooks that are called
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor to collect status. Status should be queryable by
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor HTTP or SNMP?
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor jerenkrantz says: Yawn. Who cares.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * Regex containers don't work in an intutive way
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Status: No one has come up with an efficient way to fix this
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor behavior. Dean has suggested getting rid of regex containers
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor completely.
6757f6f06a97f6d3d5e2793a65320eefd53e6d55sf OtherBill suggests: We at least seem to agree on eliminating
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor the <Container ~ foo> forms, and using only
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor <ContainerMatch foo> semantics.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor * orig_ct in the byterange/multipart handling may not be
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor needed. Apache 1.3 just never stashed "multipart" into
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor r->content_type. We should probably follow suit since the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor byterange stuff doesn't want the rest of the code to see the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor multipart content-type; the other code should still think it is
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor dealing with the <orig_ct> stuff.
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor Status: Greg volunteers to investigate (esp. since he was most
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor likely the one to break it :-)
75ae7f8e2645d58697604161bd58c35e5de0adacgryzorEXPERIMENTAL MODULES:
3016c72ae8173bcfc0989ff1b297d4f27f445108lgentis Experimental modules should eventually be be promoted to fully supported
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor status or removed from the repository entirely (ie, the
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor 'experiment' failed). This section tracks what needs to happen to
75ae7f8e2645d58697604161bd58c35e5de0adacgryzor get the modules promoted to fully supported status.