STATUS revision d415c14da6d37345738e160f785dbe8458095068
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgAPACHE 2.0 STATUS: -*-text-*-
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgLast modified at [$Date: 2002/05/26 05:45:07 $]
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.37 : in development.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.36 : released May 6, 2002 as GA.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.35 : released April 5, 2002 as GA.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.34 : tagged March 26, 2002.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.33 : tagged March 6, 2002. not released.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.32 : released Feburary 16, 2002 as beta.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.31 : rolled Feburary 1, 2002. not released.
0662ed52e814f8f08ef0e09956413a792584eddffuankg 2.0.30 : tagged January 8, 2002. not rolled.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.29 : tagged November 27, 2001. not rolled.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.28 : released November 13, 2001 as beta.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.27 : rolled November 6, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.26 : tagged October 16, 2001. not rolled.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.25 : rolled August 29, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.24 : rolled August 18, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.23 : rolled August 9, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.22 : rolled July 29, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.21 : rolled July 20, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.20 : rolled July 8, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.19 : rolled June 27, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.18 : rolled May 18, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.17 : rolled April 17, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.16 : rolled April 4, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.15 : rolled March 21, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0.14 : rolled March 7, 2001
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a9 : released December 12, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a8 : released November 20, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a7 : released October 8, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a6 : released August 18, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a5 : released August 4, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a4 : released June 7, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a3 : released April 28, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a2 : released March 31, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg 2.0a1 : released March 10, 2000
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgPlease consult the following STATUS files for information
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgon related projects:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgCURRENT RELEASE NOTES:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * 37 status: Cliff tagged JCW_PRE_2037 on Saturday as a preliminary
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg tag with the understanding that showstoppers remain and must be
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgRELEASE SHOWSTOPPERS:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * decide if the MMN bump was warranted
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Darwin: httpd won't start. Hangs looking up 0.0.0.0 during config
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg file processing.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: backtrace posted
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020525201238.P27903@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Win32: httpd won't start. There was a command line args problem
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg that got fixed, but now something else is wrong.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <5.1.0.14.2.20020525222410.02a629d0@pop3.rowe-clan.net>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <00ca01c2033e$f1c54c10$a6271b09@sashimi>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <5.1.0.14.2.20020524115533.02785e28@pop3.rowe-clan.net>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * ap_read_pid() needs cleanup w.r.t. apr_file_read_full() and EOL
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: Patch proposed
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020525200616.O27903@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * CWD issues
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <5.1.0.14.2.20020524115533.02785e28@pop3.rowe-clan.net>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <COEELENBBCHBFEPPGDOPCEPPGPAA.ake@meepzor.com>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * To high-free patch or not to high-free patch?
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <JLEGKKNELMHCJPNMOKHOGEIIFOAA.striker@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <1022371367.23007.13.camel@mypc1.pacbell.net>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Need consensus and/or "fix" on mod_deflate and existing encodings
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: Patch proposed
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020520151226.K15813@lyra.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <3CF05078.8040907@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Find a better name for ap_signal_server()
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <m37kltilb3.fsf@rdu88-251-253.nc.rr.com>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * apr_brigade_write() is not flushing in all cases it should
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: Cliff will fix this
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * mod_suexec issues seem to be at critical mass
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: Patches proposed
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * need consensus on Cliff's /dev/random vs. /dev/urandom question.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Is there a better alternative than picking strictly one or the other?
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <Pine.LNX.4.44.0205251718300.31784-100000@deepthought.cs.virginia.edu>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <20020522202404.D27903@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg <20020522210345.E2800@clove.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * server pushed CGI's not working. (Is this a showstopper??)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <3CE15B85.2FF45121@apache.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * mod_cache content-type issues (Is this a showstopper??)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: patch proposed
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <3CECFD8B.9050303@fokus.gmd.de>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgCURRENT VOTES:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Should we always build [support*] binaries statically unless otherwise
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020129210006.B23512@Lithium.MeepZor.Com>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg +1: Ken, *wrowe [they are PITAs on OSX]
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg -1: Justin, Ian
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * If the parent process dies, should the remaining child processes
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg "gracefully" self-terminate. Or maybe we should make it a runtime
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg option, or have a concept of 2 parent processes (one being a
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg "hot spare").
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Self-destruct: Ken, Martin
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Not self-destruct: BrianP, Ian, Cliff, BillS
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Make it runtime configurable: Aaron, Jim, Justin
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Have 2 parents: +1: Jim
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg -1: Justin, wrowe [for 2.0]
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg +0: Martin (while standing by, could it do
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg something useful?)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Make the worker MPM the default MPM for threaded Unix boxes.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg +1: Justin, Ian, Cliff, BillS
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg +0: BrianP, Aaron (mutex contention is looking better with the
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg latest code, let's continue tuning and testing)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Change the default config so that we add a ServerToken Minimal
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg to the config. Possibly go one step further and add a option
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg to just report '2.0' instead of '2.0.x'
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg +1: IanH, BrianP
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg -1: Greg, Cliff, Justin
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg I use the default response all the time to verify that a
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg module is present and at the proper version. This information
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg is also very handy for the module surveys, to determine what
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg modules are out there and in prevalent use (see
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg securityspace.com; frickin' JServ is still increasing in
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg numbers!). Security conscious people can change this on their
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg own, when required. Removing the information doesn't remove
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg any future vulnerabilities. Assuming that a vulnerability
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg occurred, I highly doubt that somebody would actually bother
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg to *test* the version reported in the response before
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg attempting to use the vulnerability, so trying to hide the
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg information isn't all that useful.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankgRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Get mod_cache/mod_mem_cache out of experimental (still some
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg work items left to complete)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * The 2.0.36 worker MPM graceless shutdown changes work but are
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg a bit clunky on some platforms; eg, on Linux, the loop to
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg join each worker thread seems to hang, and the parent ends up
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg killing off the child with SIGKILL. But at least it shuts down.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * We do not properly substitute the prefix-variables in the configuration
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg scripts or generated-configs. (i.e. if sysconfdir is etc,
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg httpd-std.conf points to conf.)
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * If any request gets through ap_process_request_internal() and is
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg scheduled to be served by the core handler, without a flag that this
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg r->filename was tested by dir/file_walk, we need to 500 at the very
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg end of the ap_process_request_internal() processing so sub_req-esters
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg know this request cannot be run. This provides authors of older
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg modules better compatibility, while still improving the security and
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg robustness of 2.0.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Status: still need to decide where this goes, OtherBill comments...
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg [Deleted comments regarding the ap_run_handler phase, as irrelevant
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg as BillS points out that "common case will be caught in
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg default_handler already (with the r->finfo.filetype == 0 check)"
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg and the issue is detecting this -before- we try to run the req.]
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg gregames says: can this happen somehow without a broken module
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg being involved? If not, why waste cycles trying to defend against
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg potential broken modules? It seems futile.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg wrowe counters: no, it shouldn't happen unless the module is broken.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg But the right answer is to fail the request up-front in dir/file
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg walk if the path was entirely invalid; and we can't do that either
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg or we break modules that are unwilling to hook map_to_storage.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Rewrite core_output_filter. It is nearly impossible to support
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg it with predictable results as it is implemented now.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg how the Perchild MPM should be re-written. It hasn't worked
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg correctly since filters were added because it wasn't possible to
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg get the content that had already been written and the socket at
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg the same time. This mode lets us do that, so the MPM can be
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * htpasswd blindly processes the file you give it, and does no
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg sanity checking before totally corrupting whatever file it was
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg you thought you had. It should check the input file and bail
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg if it finds non-comment lines that do not contain exactly 1
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg ':' character.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020217150457.A31632@clove.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Can a static httpd be built reliably?
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020207142751.T31582@clove.org>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * [Ken] Test suite failures:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg o worker is also failing some of the 'cgi' subtests
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg (see <URL:http://Source-Zone.Org/Apache/regression/>):
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Justin says: "Worker should be fine and passes httpd-test here.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg If you can provide evidence that it can be reproduced
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg outside of httpd-test, then it's a showstopper. I
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg think it's a perl or a httpd-test problem."
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Not a showstopper: Justin
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg removed if possible.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * There is a bug in how we sort some hooks, at least the pre-config
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg hook. The first time we call the hooks, they are in the correct
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg order, but the second time, we don't sort them correctly. Currently,
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg the modules/http/config.m4 file has been renamed to
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg modules/http/config2.m4 to work around this problem, it should moved
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg back when this is fixed. rbb
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Justin says: "Is this really a showstopper? This has been here
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg forever. What's wrong? Does this have to do with
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg autoconf or m4?"
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Not a showstopper: Justin, BrianP, trawick, gregames
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * The Add...Filter and Set...Filter directives do not allow the
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg administrator to order filters, beyond the order of filename (mime)
0662ed52e814f8f08ef0e09956413a792584eddffuankg extensions. It isn't clear if Set...Filter(s) should be inserted
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg before or after the Add...Filter(s) which are ordered by sequence of
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg filename extensions. At minimum, some sort of +-[0-10] syntax seems
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg like the quickest fix for a 2.0 gold release.
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Justin says: "Could we delay this for a point release or 2.1?"
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Not a showstopper: justin, wrowe, trawick, stoddard, Jim, Ian, Aaron,
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg * Get perchild to work on platforms other than Linux. This
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg will require a portable mechanism to pass data and file/socket
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg descriptors between vhost child groups. An API was proposed
0662ed52e814f8f08ef0e09956413a792584eddffuankg on dev@apr:
ff7e89a077d93c243bd8261cf3c72b13732ab5b4fuankg Message-ID: <20020111115006.K1529@clove.org>
ap_unescape_url() in util.c). It's permitted and passed
the child_init hook (i.e. the fcntl lock needs to be resynced).
an external dependency (e.g., a database) fails, et cetera.
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
The current porting state is summarized in modules/ssl/README. The
(1) stablizing/optimizing the SSL filter logic
* Combine log_child and piped_log_spawn. Clean up http_log.c.
* Win32: Migrate the MPM over to use APR thread/process calls. This
losing error status (i.e. throwing away the error returned by a
* All DBMs suffer from confusion in support/dbmmanage (perl script) since
* Explore use of a post-config hook for the code in http_main.c which
* (possibly) use UUIDs in mod_unique_id and/or mod_usertrack
* shift stuff to mod_core.h
rand.c, at least.) This could be resolved with an SSL library, or
- Bring the Win9xConHook.dll from 1.3 into 2.0 (no sense till it
Message-ID: <Pine.LNX.4.44.0203011354090.16457-200000@deepthought
* mod_cache: CacheEnable/CacheDisable should accept regular expressions.
* mod_mem_cache/mod_disk_cache: Need to be able to query cache
* mod_mem_cache/mod_disk_cache: Complete implementing config
* Sample config for mod_cache/mod_mem_cache/mod_disk_cache for
inclusion into httpd.conf.
* mod_cache/mod_mem_cache/mod_disk_cache: Documentation.
Using NIS passwd.byname dbm files with AuthDBMUserFile
setlogin() is not called, causing problems with e.g. identd
add allow,deny/deny,allow warning to mod_access
A small addition to rotatelogs.c to improve program functionality.
Feedback/Comment on APACI
Inclusion of RPM spec file in CVS/distributions
* orig_ct in the byterange/multipart handling may not be
Solaris 8.x/sparc yes Jim Jagielski