STATUS revision a74ee4396fe11ffc1ca05837a59e497c905eedc3
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesAPACHE 2.3 STATUS: -*-text-*-
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesLast modified at [$Date$]
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesThe current version of this file can be found at:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesDocumentation status is maintained seperately and can be found at:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * docs/STATUS in this source tree, or
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesConsult the following STATUS files for information on related projects:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/apr/apr/trunk/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/apr/apr-util/trunk/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesPatches considered for backport are noted in their branches' STATUS:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesRelease history:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes [NOTE that x.{odd}.z versions are strictly Alpha/Beta releases,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes while x.{even}.z versions are Stable/GA releases.]
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.6 : In development
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.5 : Released on January 26, 2010.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.4 : Released on December 8, 2009.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.3 : Tagged on November 11, 2009, not released.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.2 : Tagged on March 23, 2009, not released.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.1 : Tagged on January 2, 2009, not released.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 2.3.0 : Tagged on December 6, 2008, not released.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesContributors looking for a mission:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Just do an egrep on "TODO" or "XXX" in the source.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Review the bug database at: http://issues.apache.org/bugzilla/
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Review the "PatchAvailable" bugs in the bug database:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes https://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes After testing, you can append a comment saying "Reviewed and tested".
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Open bugs in the bug database.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCURRENT RELEASE NOTES:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesRELEASE SHOWSTOPPERS:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes FOR GA:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes FOR BETA:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Modules without documentation need to be moved to experimental or be
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes removed.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Not all MPMs are updated to set conn_rec::current_thread correctly.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes (Prefork, Worker, Event, Simple are updated).
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes FOR NEXT ALPHA:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes OLD ISSUES THAT WERE THOUGHT TO BE SHOWSTOPPERS FOR 2.2 BUT OBVIOUSLY WEREN'T:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Handling of non-trailing / config by non-default handler is broken
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes jerenkrantz asks: Why should this block a release?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes wsanchez agrees: this may be a change in behavior, but isn't
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes clearly wrong, and even if so, it doesn't seem like a
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes showstopper.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * the edge connection filter cannot be removed
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes jerenkrantz asks: Why should this block a release?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes stas replies: because it requires a rewrite of the filters stack
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes implementation (you have suggested that) and once 2.2 is
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes released you can't do that anymore.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes pgollucci: this affects mod_perl I'm pretty sure.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCURRENT VOTES:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * If the parent process dies, should the remaining child processes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes "gracefully" self-terminate. Or maybe we should make it a runtime
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes option, or have a concept of 2 parent processes (one being a
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes "hot spare").
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Self-destruct: Ken, Martin, Lars
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Not self-destruct: BrianP, Ian, Cliff, BillS
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd, pgollucci
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes /* The below was a concept on *how* to handle the problem */
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Have 2 parents: +1: jim
0a39e7683f6611d66c55712f50bb240428d832a1bnicholes -1: Justin, wrowe, rederpj, nd, pgollucci
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes +0: Lars, Martin (while standing by, could it do
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes something useful?)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Make the worker MPM the default MPM for threaded Unix boxes.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd, pgollucci
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes +0: BrianP, Aaron (mutex contention is looking better with the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes latest code, let's continue tuning and testing), rederpj, jim
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes -0: Lars
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes pquerna: Do we want to change this for *2.4*?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes wrowe: Replies "yes"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Name the Server (version 2.4 or 3.0, depending on the final call)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Recent discussion indicates we should designate a (short name).
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes This is not yet a [Vote] - Your nominations please:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Apache HTTP Server (httpd)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Patches submitted to the bug database:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2&keywords=PatchAvailable
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Filter stacks and subrequests, redirects and fast redirects.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes There's at least one PR that suffers from the current unclean behaviour
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes (which lets the server send garbage): PR 17629
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes nd says: Every subrequest should get its own filter stack with the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes subreq_core filter as bottom-most. That filter does two things:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes - swallow EOS buckets
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes - redirect the data stream to the upper request's (rr->main)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes filter chain directly after the subrequest's starting
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes point.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Once we have a clean solution, we can try to optimize
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes it, so that the server won't be slow down too much.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * RFC 2616 violations.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Closed PRs: 15857.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes 16138, 16139, 16140, 16142, 16518, 16520, 16521,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes jerenkrantz says: need to decide how many we need to backport and/or
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes if these rise to showstopper status.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes out of this list, without reviewing them individually.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * There is a bug in how we sort some hooks, at least the pre-config
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes hook. The first time we call the hooks, they are in the correct
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes order, but the second time, we don't sort them correctly. Currently,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes the modules/http/config.m4 file has been renamed to
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes modules/http/config2.m4 to work around this problem, it should moved
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes back when this is fixed.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes OtherBill offers that this is a SERIOUS problem. We do not sort
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes correctly by the ordering arguments passed to the register hook
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes functions. This was proven when I reordered the open_logs hook
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes to attempt to open the error logs prior to the access logs. Possibly
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes the entire sorting code needs to be refactored.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * pipes deadlock on all platforms with limited pipe buffers (e.g. both
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Linux and Win32, as opposed to only Win32 on 1.3). The right solution
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * All handlers should always send content down even if r->header_only
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes is set. If not, it means that the HEAD requests don't generate the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes same headers as a GET which is wrong.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * exec cmd and suexec arg-passing enhancements
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Status: Patches proposed
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes (see the "proc.patch" and "suexec-shell.patch" links in this message)
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * The 2.0.36 worker MPM graceless shutdown changes work but are
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes a bit clunky on some platforms; eg, on Linux, the loop to
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes join each worker thread seems to hang, and the parent ends up
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes killing off the child with SIGKILL. But at least it shuts down.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes chrisd: Has this been fixed by the changes for PR 38737?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * We do not properly substitute the prefix-variables in the configuration
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes scripts or generated-configs. (i.e. if sysconfdir is etc,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes httpd-std.conf points to conf.)
9046ab142ed19505e034af0afb8c15be512b8526bnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * If any request gets through ap_process_request_internal() and is
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes scheduled to be served by the core handler, without a flag that this
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes r->filename was tested by dir/file_walk, we need to 500 at the very
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes end of the ap_process_request_internal() processing so sub_req-esters
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes know this request cannot be run. This provides authors of older
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes modules better compatibility, while still improving the security and
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes robustness of 2.0.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Status: still need to decide where this goes, OtherBill comments...
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes [Deleted comments regarding the ap_run_handler phase, as irrelevant
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes as BillS points out that "common case will be caught in
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes default_handler already (with the r->finfo.filetype == 0 check)"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes and the issue is detecting this -before- we try to run the req.]
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes gregames says: can this happen somehow without a broken module
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes being involved? If not, why waste cycles trying to defend against
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes potential broken modules? It seems futile.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes wrowe counters: no, it shouldn't happen unless the module is broken.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes But the right answer is to fail the request up-front in dir/file
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes walk if the path was entirely invalid; and we can't do that either
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Can a static httpd be built reliably?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Message-ID: <20020207142751.T31582@clove.org>
e75db68cd3a838dfe6de1553907416c3834ebb40bnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes removed if possible.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Message-ID:
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Jeff wonders if we still care about this. It is no longer an
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes API issue but simply an extra trip through the brigade.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Try to get libtool inter-library dependency code working on AIX.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Justin says: If we get it working on AIX, we can enable this
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes on all platforms and clean up our build system somewhat.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Jeff says: I thought I tested a patch for you sometime in
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes January that you were going to commit within a few days.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * Handling of %2f in URIs. Currently both 1.3 and 2.0
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes completely disallow %2f in the request URI path (see
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes ap_unescape_url() in util.c). It's permitted and passed
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes through in the query string, however. Roy says the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes original reason for disallowing it, from five years ago,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes was to protect CGI scripts that applied PATH_INFO to
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes a filesystem location and which might be tricked by
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes ..%2f..%2f(...). We *should* allow path-info of the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes form 'http://foo.com/index.cgi/path/to/path%2finfo'.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Since we've revamped a lot of our processing of path
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes segments, it would be nice to allow this, or at least
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes allow it conditionally with a directive.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes OtherBill adds that %2f as the SECOND character of a multibyte
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes sequence causes the request to fail! This happens notably in
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes the ja-jis encoding.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * There is increasing demand from module writers for an API
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes that will allow them to control the server � la apachectl.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Reasons include sole-function servers that need to die if
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes an external dependency (e.g., a database) fails, et cetera.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes Perhaps something in the (ever more abused) scoreboard?
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes On the other hand, we already have a pipe that goes between parent
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes and child for graceful shutdown events, along with an API that
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes can be used to send a message down that pipe. In threaded MPMs,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes it is easy enough to make that one pipe be used for graceful
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes and graceless events, and it is also easy to open that pipe
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes to both parent and child for writing. Then we just need to
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes figure out how to do graceless on non-threaded MPMs.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes * 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.
striker: See the thread starting with Message-ID:
JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
* 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.
stoddard: 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.
* Eliminate unnecessary creation of pipes in mod_cgid
* Combine log_child and piped_log_spawn. Clean up http_log.c.
Common logging API.
* 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.
* 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)
* 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)
* Fix the worker MPM to use POD to kill child processes instead
of ap_os_killpg, regardless of how they should die.
chrisd: Is this done, by any chance? See r92598 and r93358.
* 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>
* APXS either needs to be fixed completely for use when apr is out of tree,
or it should drop query mode altogether, and we just grow an
httpd-config or similar arrangement.
To quote a discussion in STATUS earlier:
thommay: this doesn't fix all the problems with apxs and out of
tree apr/apr-util, but it's a good start. There's still the
query cases; but I'm beginning to think that in these cases
the app should be querying ap{r,u}-config directly
deprecate -q: add htpd-config: gstein, pquerna, minfrin, pgollucci
other:
TODO ISSUES REMAINING IN MOD_SSL:
* Do we need SSL_set_read_ahead()?
* the ssl_expr api is NOT THREAD SAFE. race conditions exist:
-in ssl_expr_comp() if SSLRequire is used in .htaccess
(ssl_expr_info is global)
-is ssl_expr_eval() if there is an error
(ssl_expr_error is global)
* SSLRequire directive (parsing of) leaks memory
* Diffie-Hellman-Parameters for temporary keys are hardcoded in
ssl_engine_dh.c, while the comment in ssl_engine_kernel.c says:
"it is suggested that keys be changed daily or every 500
transactions, and more often if possible."
* ssl_var_lookup could be rewritten to be MUCH faster
* CRL callback should be pluggable
* session cache store should be pluggable
* init functions should return status code rather than ssl_die()
* ssl_engine_pphrase.c needs to be reworked so it is generic enough
to also decrypt proxy keys
* output warning when allowing SSL v2.0 ? its so old
WISH LIST
* mod_proxy: Ability to run SSL over proxy gateway connections,
encrypting (or reencrypting) at the proxy.
* mod_cache: Handle ESI tags.
* mod_cache: Resolve issue of how to cache page fragements (or perhaps
-if- we want to cache page fragements). Today, mod_cache/mod_mem_cache
will cache #include 'virtual' requests (but not #include 'file'
requests). This was accomplished by making CACHE_IN a
CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
filter. But now responses cannot be cached that include the
effects of having been run through CONTENT_SET filters
(mod_deflate, mod_expires, etc). We could rerun all the
CONTENT_SET filters on the cached response, but this will not
work in all cases. For example, mod_expires relies on installing
the EXPIRATION filter during fixups. Contents served out of
mod_cache (out of the quick_handler) bypass -all- the request
line server hooks (Ryan really hated this. It is great for
performance, but bad because of the complications listed above).
mod_cache/mod_mem_cache/mod_disk_cache:
* mod_mem_cache: Consider adding a RevalidateTimeout directive to
specify time at which local cached content is to be revalidated
(ie, underlying file stat'ed to see if it has changed).
* mod_cache: CacheEnable/CacheDisable should accept regular expressions.
jerenkrantz says: Too slow. Get regexs away from speedy caches by
default. Introduce a new CacheEnableRegex if you want.
* 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?
jerenkrantz says: Yawn. Who cares.
* 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.
* 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 :-)
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.