454N/AAPACHE 2.3 STATUS: -*-text-*-
454N/ALast modified at [$Date$]
471N/AThe current version of this file can be found at:
3252N/ADocumentation status is maintained seperately and can be found at:
2245N/AConsult the following STATUS files for information on related projects:
454N/APatches considered for backport are noted in their branches' STATUS:
454N/A 2.3.1 : Tagged on January 2, 2009.
454N/A 2.3.0 : Tagged on December 6, 2008, not released.
454N/AContributors looking for a mission:
454N/A * Just do an egrep on "TODO" or "XXX" in the source.
454N/A * Review the "PatchAvailable" bugs in the bug database:
454N/A After testing, you can append a comment saying "Reviewed and tested".
454N/A * Open bugs in the bug database.
454N/A * Not all MPMs are updated to set conn_rec::current_thread correctly.
454N/A (Prefork, Worker, Event, Simple are updated).
454N/A * Handling of non-trailing / config by non-default handler is broken
454N/A jerenkrantz asks: Why should this block a release?
454N/A wsanchez agrees: this may be a change in behavior, but isn't
454N/A clearly wrong, and even if so, it doesn't seem like a
454N/A * the edge connection filter cannot be removed
454N/A jerenkrantz asks: Why should this block a release?
454N/A stas replies: because it requires a rewrite of the filters stack
454N/A implementation (you have suggested that) and once 2.2 is
454N/A released you can't do that anymore.
454N/A pgollucci: this affects mod_perl I'm pretty sure.
454N/A * If the parent process dies, should the remaining child processes
454N/A "gracefully" self-terminate. Or maybe we should make it a runtime
471N/A option, or have a concept of 2 parent processes (one being a
454N/A See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
454N/A Self-destruct: Ken, Martin, Lars
454N/A Not self-destruct: BrianP, Ian, Cliff, BillS
454N/A Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd
454N/A /* The below was a concept on *how* to handle the problem */
454N/A Have 2 parents: +1: jim
454N/A -1: Justin, wrowe, rederpj, nd, pgollucci
454N/A +0: Lars, Martin (while standing by, could it do
454N/A * Make the worker MPM the default MPM for threaded Unix boxes.
454N/A +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd, pgollucci
454N/A +0: BrianP, Aaron (mutex contention is looking better with the
454N/A latest code, let's continue tuning and testing), rederpj, jim
454N/A pquerna: Do we want to change this for *2.4*?
454N/ARELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
454N/A * Patches submitted to the bug database:
454N/A * Filter stacks and subrequests, redirects and fast redirects.
454N/A There's at least one PR that suffers from the current unclean behaviour
454N/A (which lets the server send garbage): PR 17629
454N/A nd says: Every subrequest should get its own filter stack with the
454N/A subreq_core filter as bottom-most. That filter does two things:
454N/A - redirect the data stream to the upper request's (rr->main)
454N/A filter chain directly after the subrequest's starting
454N/A Once we have a clean solution, we can try to optimize
454N/A it, so that the server won't be slow down too much.
454N/A Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
454N/A 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
454N/A 16138, 16139, 16140, 16142, 16518, 16520, 16521,
454N/A jerenkrantz says: need to decide how many we need to backport
and/or 454N/A if these rise to showstopper status.
454N/A wrowe suggests: it would be nice to see "MUST"
v.s. "SHOULD"
v.s. "MAY"
454N/A out of this list, without reviewing them individually.
454N/A * There is a bug in how we sort some hooks, at least the pre-config
454N/A hook. The first time we call the hooks, they are in the correct
454N/A order, but the second time, we don't sort them correctly. Currently,
454N/A back when this is fixed.
454N/A OtherBill offers that this is a SERIOUS problem. We do not sort
454N/A correctly by the ordering arguments passed to the register hook
454N/A functions. This was proven when I reordered the open_logs hook
454N/A to attempt to open the error logs prior to the access logs. Possibly
454N/A the entire sorting code needs to be refactored.
454N/A * pipes deadlock on all platforms with limited pipe buffers (
e.g. both
454N/A Linux and Win32, as opposed to only Win32 on 1.3). The right solution
454N/A is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
454N/A for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
454N/A * All handlers should always send content down even if r->header_only
454N/A is set. If not, it means that the HEAD requests don't generate the
454N/A same headers as a GET which is wrong.
454N/A * exec cmd and suexec arg-passing enhancements
454N/A Status: Patches proposed
454N/A Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
454N/A * The 2.0.36 worker MPM graceless shutdown changes work but are
454N/A a bit clunky on some platforms; eg, on Linux, the loop to
454N/A join each worker thread seems to hang, and the parent ends up
454N/A killing off the child with SIGKILL. But at least it shuts down.
454N/A chrisd: Has this been fixed by the changes for PR 38737?
454N/A * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
454N/A posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
454N/A * We do not properly substitute the prefix-variables in the configuration
454N/A scripts or generated-configs. (
i.e. if sysconfdir is etc,
454N/A * If any request gets through ap_process_request_internal() and is
454N/A scheduled to be served by the core handler, without a flag that this
454N/A end of the ap_process_request_internal() processing so sub_req-esters
454N/A know this request cannot be run. This provides authors of older
454N/A modules better compatibility, while still improving the security and
454N/A Status: still need to decide where this goes, OtherBill comments...
454N/A Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
454N/A [Deleted comments regarding the ap_run_handler phase, as irrelevant
454N/A as BillS points out that "common case will be caught in
454N/A and the issue is detecting this -before- we try to run the req.]
454N/A gregames says: can this happen somehow without a broken module
454N/A being involved? If not, why waste cycles trying to defend against
454N/A potential broken modules? It seems futile.
454N/A wrowe counters: no, it shouldn't happen unless the module is broken.
454N/A But the right answer is to fail the request up-front in
dir/file 454N/A walk if the path was entirely invalid; and we can't do that either
454N/A UNTIL 2.1 or we break modules that haven't hooked map_to_storage.
454N/A * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me
454N/A how the Perchild MPM should be re-written. It hasn't worked
454N/A correctly since filters were added because it wasn't possible to
454N/A get the content that had already been written and the socket at
454N/A the same time. This mode lets us do that, so the MPM can be
454N/A * Can a static httpd be built reliably?
454N/A Message-ID: <20020207142751.T31582@clove.org>
454N/A * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
454N/A <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
454N/A Jeff wonders if we still care about this. It is no longer an
454N/A API issue but simply an extra trip through the brigade.
454N/A * Get perchild to work on platforms other than Linux. This
454N/A descriptors between vhost child groups. An API was proposed
454N/A Message-ID: <20020111115006.K1529@clove.org>
454N/A * Try to get libtool inter-library dependency code working on AIX.
454N/A Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
454N/A Justin says: If we get it working on AIX, we can enable this
454N/A on all platforms and clean up our build system somewhat.
454N/A Jeff says: I thought I tested a patch for you sometime in
454N/A January that you were going to commit within a few days.
454N/A * Handling of %2f in URIs. Currently both 1.3 and 2.0
454N/A completely disallow %2f in the request URI path (see
454N/A ap_unescape_url() in
util.c). It's permitted and passed
454N/A through in the query string, however. Roy says the
454N/A original reason for disallowing it, from five years ago,
454N/A was to protect CGI scripts that applied PATH_INFO to
454N/A a filesystem location and which might be tricked by
454N/A ..%2f..%2f(...). We *should* allow path-info of the
454N/A Since we've revamped a lot of our processing of path
620N/A segments, it would be nice to allow this, or at least
454N/A allow it conditionally with a directive.
2245N/A OtherBill adds that %2f as the SECOND character of a multibyte
454N/A sequence causes the request to fail! This happens notably in
454N/A * There is increasing demand from module writers for an API
454N/A that will allow them to control the server � la apachectl.
454N/A Reasons include sole-function servers that need to die if
454N/A an external dependency (
e.g., a database) fails, et cetera.
454N/A Perhaps something in the (ever more abused) scoreboard?
454N/A On the other hand, we already have a pipe that goes between parent
454N/A and child for graceful shutdown events, along with an API that
454N/A can be used to send a message down that pipe. In threaded MPMs,
454N/A it is easy enough to make that one pipe be used for graceful
454N/A and graceless events, and it is also easy to open that pipe
454N/A to both parent and child for writing. Then we just need to
454N/A figure out how to do graceless on non-threaded MPMs.
454N/A * Allow the DocumentRoot directive within <Location > scopes? This
454N/A and in-your-face.) DocumentRoot unset would be accepted [and would
454N/A not permit content to be served, only virtual resources such as
454N/A server-info or server-status.
454N/A This proposed change would _not_ depricate Alias.
454N/A striker: See the thread starting with Message-ID:
454N/A JLEGKKNELMHCJPNMOKHOGEEJFBAA.striker@apache.org.
454N/A * Win32: Rotatelogs sometimes is not terminated when Apache
454N/A goes down hard. FirstBill was looking at possibly tracking the
454N/A child's-child processes in the parent process.
454N/A stoddard: Shared scoreboard might offer a good way for the parent
454N/A to keep track of 'other child' processes and whack them if the child
454N/A Other thoughts on walking the process chain using the NT kernel
454N/A have also been proposed on APR.
454N/A * Eliminate unnecessary creation of pipes in mod_cgid
454N/A * Platforms that do not support fork (primarily Win32 and AS/400)
454N/A Architect start-up code that avoids initializing all the modules
454N/A 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.
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?
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.
* 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:
<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
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
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
"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()
to also decrypt proxy keys
* output warning when allowing SSL v2.0 ? its so old
* 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
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_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).
jerenkrantz says: Too slow. Get regexs away from speedy caches by
default. Introduce a new CacheEnableRegex if you want.
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
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
OtherBill suggests: We at least seem to agree on eliminating
the <Container ~ foo> forms, and using only
<ContainerMatch foo> semantics.
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 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.