APACHE 2.0 STATUS: -*-text-*-
-Last modified at [$Date: 2001/11/28 07:11:44 $]
+Last modified at [$Date: 2002/01/02 08:05:15 $]
Release:
RELEASE SHOWSTOPPERS:
+ * ap_directory_walk skips some per-dir config merge functions
+ if there is no "<Directory />" block in the configuration
+ Message-ID: <m3itbdiijq.fsf@rdu163-40-092.nc.rr.com>
+
+ * Test suite failures:
+ o perchild doesn't even build
+ o both worker and prefork are failing some of the 'chunked' subtests
+ o worker is also failing some of the 'cgi' subtests
+ (see <URL:http://Source-Zone.Org/Apache/regression/>):
+
* If any request gets to the core handler, without a flag that this
r->filename was tested by dir/file_walk, we need to 500 at the very
end of the ap_process_request_internal() processing. This provides
Status: Bill has some code in his tree that accomplishes
this, and will commit it Friday after it's tested.
+ * Fold mod_auth_db features back into mod_auth_dbm, and depricate it.
+ This can't wait until we have a 2.0-gold release, if folks need
+ to move over to auth_dbm, we can't do that to them after 2.0 gold.
+ Status: Ian says.. auth_dbm can now handle multiple DBM types,
+ is this still an issue?
+ Vote: Remove mod_auth_db
+ +1: Justin
+
+ * Convert all instances of the old apr_lock_t type to the new
+ types (once they are fully supported in APR).
+ Status: Aaron is working on converting INTRAPROCESS
+ to apr_thread_mutex_t types. Full replacements for
+ LOCKALL and CROSS_PROCESS are not yet complete on all
+ platforms, and should only be used in MPMs like worker
+ with limited OS exposure.
+
+ * ap_create_scoreboard() can exit the process, leaving stuff like
+ mod_cgid's daemon process stranded. Either ap_create_scoreboard()
+ needs to be called at a different time or the pre-mpm hook needs
+ to be able to return an error code.
+
+RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
+
+ * Handling of %2f in URIs. Currently both 1.3 and 2.0
+ completely disallow %2f in the request URI path (see
+ ap_unescape_url() in util.c). It's permitted and passed
+ through in the query string, however. Roy says the
+ original reason for disallowing it, from five years ago,
+ was to protect CGI scripts that applied PATH_INFO to
+ a filesystem location and which might be tricked by
+ ..%2f..%2f(...). We *should* allow path-info of the
+ form 'http://foo.com/index.cgi/path/to/path%2finfo'.
+ Since we've revamped a lot of our processing of path
+ segments, it would be nice to allow this, or at least
+ allow it conditionally with a directive.
+
+ * FreeBSD, threads, and worker MPM. All seems to work fine
+ if you only have one worker process with many threads. Add
+ a second worker process and the accept lock seems to be
+ lost. This might be an APR issue with how it deals with
+ the child_init hook (i.e. the fcntl lock needs to be resynced).
+ More examination and analysis is required.
+
+ * There is increasing demand from module writers for an API
+ that will allow them to control the server à la apachectl.
+ Reasons include sole-function servers that need to die if
+ an external dependency (e.g., a database) fails, et cetera.
+ Perhaps something in the (ever more abused) scoreboard?
+ rbb: I don't believe the scoreboard is the correct mechanism
+ for this. We already have a pipe that goes between parent
+ and child for graceful shutdown events, along with an API that
+ can be used to send a message down that pipe. In threaded MPMs,
+ it is easy enough to make that one pipe be used for graceful
+ and graceless events, and it is also easy to open that pipe
+ to both parent and child for writing. Then we just need to figure
+ out how to do graceless on non-threaded MPMs.
+
* revamp the input filter behavior, per discussions since
February (and especially at the hackathon last
April). Specifically, ap_get_brigade will return a brigade with
- thoughts on filter modes:
Message-ID: <021b01c14dee$09782af0$93c0b0d0@roweclan.net>
- * Fold mod_auth_db features back into mod_auth_dbm, and depricate it.
- This can't wait until we have a 2.0-gold release, if folks need
- to move over to auth_dbm, we can't do that to them after 2.0 gold.
-
- * Convert all instances of the old apr_lock_t type to the new
- types (once they are fully supported in APR).
- Status: Aaron is working on converting INTRAPROCESS
- to apr_thread_mutex_t types. Full replacements for
- LOCKALL and CROSS_PROCESS are not yet complete on all
- platforms, and should only be used in MPMs like worker
- with limited OS exposure.
-
-RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
-
* 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
server-info or server-status.
This proposed change would _not_ depricate Alias.
- * add mod_gz to httpd-2.0 (in modules/experimental/)
- +1: Greg, Justin, ben, Ken, Jeff, Bill, Ian
- 0: Cliff (there's now another candidate to be evaluated)
- 0: Jim, Aaron (premature decision at present, IMO)
- -0: Doug, Ryan
-
- * daedalus: mod_cgid and suexec have a problem co-existing. suexec
- sees a null command string sometimes. The problem happens when
- you access bugs.apache.org, then click on the "search the bug db"
- button.
-
* 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.
a userlist via dbm, which has to remain readable between
builds/machines, etc. The use-multiple database schema
for apr-util would let us do this with just apr, though."
+ Ian says: "multi-dbm is in, but it still has ndbm support hardcoded
+ is this still required? isn't ndbm supported via gdbm?"
+
* Integrate mod_dav.
Some additional items remaining:
-0: Aaron (premature decision, needs more discussion)
-0: Cliff (I think the default config should be the safest possible)
+ * Fix the worker MPM to use POD to kill child processes instead
+ of ap_os_killpg, regardless of how they should die. (Ryan Bloom)
+
PRs that have been suspended forever waiting for someone to
put them into 'the next release':