STATUS revision a74ee4396fe11ffc1ca05837a59e497c905eedc3
e9b6af083e34e2397a8ddbe9781920733d09d151Ted GouldAPACHE 2.3 STATUS: -*-text-*-
e9b6af083e34e2397a8ddbe9781920733d09d151Ted GouldLast modified at [$Date$]
e9b6af083e34e2397a8ddbe9781920733d09d151Ted GouldThe current version of this file can be found at:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzDocumentation status is maintained seperately and can be found at:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * docs/STATUS in this source tree, or
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzConsult the following STATUS files for information on related projects:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzPatches considered for backport are noted in their branches' STATUS:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzRelease history:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz while x.{even}.z versions are Stable/GA releases.]
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.6 : In development
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.5 : Released on January 26, 2010.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.4 : Released on December 8, 2009.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.3 : Tagged on November 11, 2009, not released.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.2 : Tagged on March 23, 2009, not released.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.1 : Tagged on January 2, 2009, not released.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 2.3.0 : Tagged on December 6, 2008, not released.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzContributors looking for a mission:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Just do an egrep on "TODO" or "XXX" in the source.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Review the bug database at: http://issues.apache.org/bugzilla/
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Review the "PatchAvailable" bugs in the bug database:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz After testing, you can append a comment saying "Reviewed and tested".
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Open bugs in the bug database.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzCURRENT RELEASE NOTES:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzRELEASE SHOWSTOPPERS:
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth * Modules without documentation need to be moved to experimental or be
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Not all MPMs are updated to set conn_rec::current_thread correctly.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (Prefork, Worker, Event, Simple are updated).
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz FOR NEXT ALPHA:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Handling of non-trailing / config by non-default handler is broken
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz jerenkrantz asks: Why should this block a release?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz wsanchez agrees: this may be a change in behavior, but isn't
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz clearly wrong, and even if so, it doesn't seem like a
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz showstopper.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * the edge connection filter cannot be removed
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz jerenkrantz asks: Why should this block a release?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz stas replies: because it requires a rewrite of the filters stack
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz implementation (you have suggested that) and once 2.2 is
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz released you can't do that anymore.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz pgollucci: this affects mod_perl I'm pretty sure.
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworthCURRENT VOTES:
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller * If the parent process dies, should the remaining child processes
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller "gracefully" self-terminate. Or maybe we should make it a runtime
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth option, or have a concept of 2 parent processes (one being a
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller "hot spare").
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Self-destruct: Ken, Martin, Lars
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Not self-destruct: BrianP, Ian, Cliff, BillS
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd, pgollucci
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz /* The below was a concept on *how* to handle the problem */
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller Have 2 parents: +1: jim
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth -1: Justin, wrowe, rederpj, nd, pgollucci
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz +0: Lars, Martin (while standing by, could it do
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz something useful?)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Make the worker MPM the default MPM for threaded Unix boxes.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd, pgollucci
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz +0: BrianP, Aaron (mutex contention is looking better with the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz latest code, let's continue tuning and testing), rederpj, jim
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz pquerna: Do we want to change this for *2.4*?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz wrowe: Replies "yes"
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Name the Server (version 2.4 or 3.0, depending on the final call)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Recent discussion indicates we should designate a (short name).
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz This is not yet a [Vote] - Your nominations please:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Apache HTTP Server (httpd)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
4325c73c705ad4c09590f8d4f1e62d849eeda096cilix * Patches submitted to the bug database:
67a4dc11b52e8d742e1c628c18fcea27423c9995cilix http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Filter stacks and subrequests, redirects and fast redirects.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz There's at least one PR that suffers from the current unclean behaviour
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (which lets the server send garbage): PR 17629
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz nd says: Every subrequest should get its own filter stack with the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz subreq_core filter as bottom-most. That filter does two things:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz - swallow EOS buckets
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz - redirect the data stream to the upper request's (rr->main)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz filter chain directly after the subrequest's starting
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Once we have a clean solution, we can try to optimize
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz it, so that the server won't be slow down too much.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * RFC 2616 violations.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Closed PRs: 15857.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz 16138, 16139, 16140, 16142, 16518, 16520, 16521,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz jerenkrantz says: need to decide how many we need to backport and/or
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz if these rise to showstopper status.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz out of this list, without reviewing them individually.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * There is a bug in how we sort some hooks, at least the pre-config
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz hook. The first time we call the hooks, they are in the correct
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz order, but the second time, we don't sort them correctly. Currently,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz the modules/http/config.m4 file has been renamed to
11677738c9eb13fc8e38618ca966739b730954c1JazzyNico modules/http/config2.m4 to work around this problem, it should moved
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz back when this is fixed.
11677738c9eb13fc8e38618ca966739b730954c1JazzyNico OtherBill offers that this is a SERIOUS problem. We do not sort
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz correctly by the ordering arguments passed to the register hook
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz functions. This was proven when I reordered the open_logs hook
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz to attempt to open the error logs prior to the access logs. Possibly
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz the entire sorting code needs to be refactored.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * pipes deadlock on all platforms with limited pipe buffers (e.g. both
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Linux and Win32, as opposed to only Win32 on 1.3). The right solution
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * All handlers should always send content down even if r->header_only
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz is set. If not, it means that the HEAD requests don't generate the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz same headers as a GET which is wrong.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * exec cmd and suexec arg-passing enhancements
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Status: Patches proposed
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (see the "proc.patch" and "suexec-shell.patch" links in this message)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * The 2.0.36 worker MPM graceless shutdown changes work but are
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz a bit clunky on some platforms; eg, on Linux, the loop to
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz join each worker thread seems to hang, and the parent ends up
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz killing off the child with SIGKILL. But at least it shuts down.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz chrisd: Has this been fixed by the changes for PR 38737?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * We do not properly substitute the prefix-variables in the configuration
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz scripts or generated-configs. (i.e. if sysconfdir is etc,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz httpd-std.conf points to conf.)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * If any request gets through ap_process_request_internal() and is
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz scheduled to be served by the core handler, without a flag that this
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz r->filename was tested by dir/file_walk, we need to 500 at the very
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz end of the ap_process_request_internal() processing so sub_req-esters
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz know this request cannot be run. This provides authors of older
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz modules better compatibility, while still improving the security and
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz robustness of 2.0.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Status: still need to decide where this goes, OtherBill comments...
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz [Deleted comments regarding the ap_run_handler phase, as irrelevant
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz as BillS points out that "common case will be caught in
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz default_handler already (with the r->finfo.filetype == 0 check)"
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz and the issue is detecting this -before- we try to run the req.]
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz gregames says: can this happen somehow without a broken module
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz being involved? If not, why waste cycles trying to defend against
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz potential broken modules? It seems futile.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz wrowe counters: no, it shouldn't happen unless the module is broken.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz But the right answer is to fail the request up-front in dir/file
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz walk if the path was entirely invalid; and we can't do that either
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller * Can a static httpd be built reliably?
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth Message-ID: <20020207142751.T31582@clove.org>
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller removed if possible.
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth Jeff wonders if we still care about this. It is no longer an
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth API issue but simply an extra trip through the brigade.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Try to get libtool inter-library dependency code working on AIX.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Justin says: If we get it working on AIX, we can enable this
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz on all platforms and clean up our build system somewhat.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Jeff says: I thought I tested a patch for you sometime in
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz January that you were going to commit within a few days.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Handling of %2f in URIs. Currently both 1.3 and 2.0
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz completely disallow %2f in the request URI path (see
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz ap_unescape_url() in util.c). It's permitted and passed
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz through in the query string, however. Roy says the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz original reason for disallowing it, from five years ago,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz was to protect CGI scripts that applied PATH_INFO to
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz a filesystem location and which might be tricked by
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz ..%2f..%2f(...). We *should* allow path-info of the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz form 'http://foo.com/index.cgi/path/to/path%2finfo'.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Since we've revamped a lot of our processing of path
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz segments, it would be nice to allow this, or at least
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz allow it conditionally with a directive.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz OtherBill adds that %2f as the SECOND character of a multibyte
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz sequence causes the request to fail! This happens notably in
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz the ja-jis encoding.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * There is increasing demand from module writers for an API
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz that will allow them to control the server � la apachectl.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Reasons include sole-function servers that need to die if
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz an external dependency (e.g., a database) fails, et cetera.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Perhaps something in the (ever more abused) scoreboard?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz On the other hand, we already have a pipe that goes between parent
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz and child for graceful shutdown events, along with an API that
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz can be used to send a message down that pipe. In threaded MPMs,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz it is easy enough to make that one pipe be used for graceful
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz and graceless events, and it is also easy to open that pipe
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz to both parent and child for writing. Then we just need to
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz figure out how to do graceless on non-threaded MPMs.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Allow the DocumentRoot directive within <Location > scopes? This
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz by a <Directory /somepath/foo> to become simply
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more legible
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz and in-your-face.) DocumentRoot unset would be accepted [and would
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz not permit content to be served, only virtual resources such as
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz server-info or server-status.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz This proposed change would _not_ depricate Alias.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz striker: See the thread starting with Message-ID:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Win32: Rotatelogs sometimes is not terminated when Apache
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz goes down hard. FirstBill was looking at possibly tracking the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz child's-child processes in the parent process.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz stoddard: Shared scoreboard might offer a good way for the parent
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz to keep track of 'other child' processes and whack them if the child
b1d0bf609336eb070d917d177e1bd2134175b19eulferikson Other thoughts on walking the process chain using the NT kernel
b1d0bf609336eb070d917d177e1bd2134175b19eulferikson have also been proposed on APR.
b1d0bf609336eb070d917d177e1bd2134175b19eulferikson * Eliminate unnecessary creation of pipes in mod_cgid
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller * Combine log_child and piped_log_spawn. Clean up http_log.c.
b1d0bf609336eb070d917d177e1bd2134175b19eulferikson Common logging API.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Platforms that do not support fork (primarily Win32 and AS/400)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Architect start-up code that avoids initializing all the modules
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz in the parent process on platforms that do not support fork.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * There are still a number of places in the code where we are
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz losing error status (i.e. throwing away the error returned by a
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz system call and replacing it with a generic error code)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Mass vhosting version of suEXEC.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * All DBMs suffer from confusion in support/dbmmanage (perl script) since
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz the dbmmanage employs the first-matched dbm format. This is not
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz necessarily the library that Apache was built with. Aught to
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz rewrite dbmmanage upon installation to bin/ with the proper library
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz for predictable mod_auth_dbm administration.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Questions; htdbm exists, time to kill dbmmanage, or does it remain
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz useful as a perl dbm management example? If we keep it,
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz do we address the issue above?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Integrate mod_dav.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Some additional items remaining:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz - case_preserved_filename stuff
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (use the new canonical name stuff?)
67a4dc11b52e8d742e1c628c18fcea27423c9995cilix - find a new home for ap_text(_header)
67a4dc11b52e8d742e1c628c18fcea27423c9995cilix - is it possible to remove the DAV: namespace stuff from util_xml?
67a4dc11b52e8d742e1c628c18fcea27423c9995cilix * ap_core_translate() and its use by mod_mmap_static and mod_file_cache
67a4dc11b52e8d742e1c628c18fcea27423c9995cilix are a bit wonky. The function should probably be exposed as a utility
28f9a94acfcc145217d0ba55ac12506557ff1db5cilix function (such as ap_translate_url2fs() or ap_validate_fs_url() or
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz something). Another approach would be a new hook phase after
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz "translate" which would allow the module to munge what the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz translation has decided to do.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz Status: Greg +1 (volunteers)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Explore use of a post-config hook for the code in http_main.c which
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz calls ap_fixup_virutal_hosts(), ap_fini_vhost_config(), and
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz ap_sort_hooks() [to reduce the logic in main()]
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * read the config tree just once, and process N times (as necessary)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * (possibly) use UUIDs in mod_unique_id and/or mod_usertrack
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * (possibly) port the bug fix for PR 6942 (segv when LoadModule is put
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz into a VirtualHost container) to 2.0.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * shift stuff to mod_core.h
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * callers of ap_run_create_request() should check the return value
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz for failure (Doug volunteers)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Fix the worker MPM to use POD to kill child processes instead
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz of ap_os_killpg, regardless of how they should die.
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller chrisd: Is this done, by any chance? See r92598 and r93358.
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Scoreboard structures could be changed in the future such that
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth proper alignment is not maintained, leading to segfaults on
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz some systems. Cliff posted a patch to deal with this issue but
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz later recanted. See this message to dev@apr.apache.org:
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth <Pine.LNX.4.44.0203011354090.16457-200000@deepthought.cs.virginia.edu>
78a4fd75621ab829ed0005b043f7262ebec13f69joelholdsworth * APXS either needs to be fixed completely for use when apr is out of tree,
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller or it should drop query mode altogether, and we just grow an
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller httpd-config or similar arrangement.
623ff472f7c7c13cbcfa9a74556cc2c4aeae337djeff_schiller To quote a discussion in STATUS earlier:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz thommay: this doesn't fix all the problems with apxs and out of
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz tree apr/apr-util, but it's a good start. There's still the
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz query cases; but I'm beginning to think that in these cases
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz the app should be querying ap{r,u}-config directly
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz deprecate -q: add htpd-config: gstein, pquerna, minfrin, pgollucci
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruzTODO ISSUES REMAINING IN MOD_SSL:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * Do we need SSL_set_read_ahead()?
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * the ssl_expr api is NOT THREAD SAFE. race conditions exist:
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz -in ssl_expr_comp() if SSLRequire is used in .htaccess
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (ssl_expr_info is global)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz -is ssl_expr_eval() if there is an error
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz (ssl_expr_error is global)
6bffd52160c0be8ad7b402099c7e1c70eeed4556joncruz * SSLRequire directive (parsing of) leaks memory
* ssl_engine_pphrase.c needs to be reworked so it is generic enough
-if- we want to cache page fragements). Today, mod_cache/mod_mem_cache
* mod_cache: CacheEnable/CacheDisable should accept regular expressions.
* mod_mem_cache/mod_disk_cache: Need to be able to query cache
* orig_ct in the byterange/multipart handling may not be