STATUS revision 942f9b7d835bb864a76719c131efcf3861450c96
2a6c49cfaef5979a5a06098f3ce987cd76769409manojAPACHE 2.1 STATUS: -*-text-*-
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddardLast modified at [$Date: 2003/12/12 10:24:59 $]
2a6c49cfaef5979a5a06098f3ce987cd76769409manojRelease [NOTE that only Alpha/Beta releases occur in 2.1 development]:
3304cbd819df02e7548e9338dc0afa8d3ba29358manoj 2.1.0 : in development
3304cbd819df02e7548e9338dc0afa8d3ba29358manojPlease consult the following STATUS files for information
2a6c49cfaef5979a5a06098f3ce987cd76769409manojon related projects:
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddardContributors looking for a mission:
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard * just do an egrep on "TODO" or "XXX" in the source.
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard * Review the "PatchAvailable" bugs in the bug database.
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard Append a comment saying "Reviewed and tested".
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard * Open bugs in the bug database.
2aae6faee508221efbeaba5547ca79b7a20ef047stoddardCURRENT RELEASE NOTES:
4065b438067f3f08d0bd98b31ac4085b581b931dstoddardRELEASE SHOWSTOPPERS:
2739add8add66e21526ce27f83c2ae133d089070rbb * Handling of non-trailing / config by non-default handler is broken
4065b438067f3f08d0bd98b31ac4085b581b931dstoddard http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2
211bf1d44f4653bf753a15740cd5ebbf330b6e93manoj * the edge connection filter cannot be removed
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2
369edcdd0a9c5516c61e736ec2a6fc8fb0d92fe2manojCURRENT VOTES:
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard * Promote mod_cache from experimental to non-experimental
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard status (keep issues noted below in EXPERIMENTAL MODULES as
85cbdc16ac57fa68ce1358a308269abcd417f4d9stoddard items to be addressed as a supported module).
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard +1: jim, bnicholes
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard -0: jerenkrantz
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard -1: stoddard
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard There are a couple of problems that need to be resolved
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard before this module is moved out of experimental.
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard 1) We need to at least review and comment on the RFC violations
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard 2) Resolve issue of how to cache page fragements (or perhaps -if- we
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard want to cache page fragements). Today, mod_cache/mod_mem_cache
d208bda4a893cc81ed5d3ed1cdd7d706e012bd42stoddard will cache #include 'virtual' requests (but not #include 'file'
75960f20f88dad6bc67892c711c429946063d133stoddard requests). This was accomplished by making CACHE_IN a
75960f20f88dad6bc67892c711c429946063d133stoddard CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE
75960f20f88dad6bc67892c711c429946063d133stoddard filter. But now responses cannot be cached that include the
75960f20f88dad6bc67892c711c429946063d133stoddard effects of having been run through CONTENT_SET filters
75960f20f88dad6bc67892c711c429946063d133stoddard (mod_deflate, mod_expires, etc). We could rerun all the
75960f20f88dad6bc67892c711c429946063d133stoddard CONTENT_SET filters on the cached response, but this will not
75960f20f88dad6bc67892c711c429946063d133stoddard work in all cases. For example, mod_expires relies on installing
75960f20f88dad6bc67892c711c429946063d133stoddard the EXPIRATION filter during fixups. Contents served out of
75960f20f88dad6bc67892c711c429946063d133stoddard mod_cache (out of the quick_handler) bypass -all- the request
75960f20f88dad6bc67892c711c429946063d133stoddard line server hooks (Ryan really hated this. It is great for
75960f20f88dad6bc67892c711c429946063d133stoddard performance, but bad because of the complications listed above).
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj jerenkrantz: There are a slew of RFC compliance bugs filed in Bugzilla
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj for mod_cache (see 'RFC 2616 violations' below). I think
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj fixing them is a pre-requisite before it isn't experimental.
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj * httpd-std.conf and friends
56ca30c968906053ae61acb218420667bb58d996rbb a) httpd-std.conf should be tailored by install (from src or
a9e07e4f90adcc7bc768db3055431c3dcd560cd1manoj binbuild) even if user has existing httpd.conf
f6a6245816cd866361da8c576b1f47c7a54b6610fanf +1: trawick, slive, gregames, ianh, Ken, wrowe, jwoolley, jim, nd,
a9e07e4f90adcc7bc768db3055431c3dcd560cd1manoj wrowe - prefer httpd.default.conf to avoid ambiguity with cvs
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj b) tailored httpd-std.conf should be copied by install to
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet -0: striker
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet c) tailored httpd-std.conf should be installed to
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet +1: slive, trawick, Ken, nd (prefer the latter), erikabele
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet d) Installing a set of default config files when upgrading a server
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet doesn't make ANY sense at all.
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet +1: ianh - medium/big sites don't use 'standard config' anyway, as it
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet usually needs major customizations
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet -1: Ken, wrowe, jwoolley, jim, nd, erikabele
8de99b4c89d4ed4292a7dca42dd8a96b9a7c456fdgaudet wrowe - diff is wonderful when comparing old/new default configs,
40a5b7189dbbb28e107bf008ee625f2f0142c2ccdgaudet even for customized sites that ianh mentions
0b0a5225c5ed94b9f689839a14842ad4a24215e9dgaudet jim - ... assuming that the default configs have been updated
0b0a5225c5ed94b9f689839a14842ad4a24215e9dgaudet with the required inline docs to explain the
0b0a5225c5ed94b9f689839a14842ad4a24215e9dgaudet * If the parent process dies, should the remaining child processes
f824925ac58ff729289c017235eeb3bdd21ec3a2stoddard "gracefully" self-terminate. Or maybe we should make it a runtime
f824925ac58ff729289c017235eeb3bdd21ec3a2stoddard option, or have a concept of 2 parent processes (one being a
f824925ac58ff729289c017235eeb3bdd21ec3a2stoddard "hot spare").
f824925ac58ff729289c017235eeb3bdd21ec3a2stoddard See: Message-ID: <3C58232C.FE91F19F@Golux.Com>
2aae6faee508221efbeaba5547ca79b7a20ef047stoddard Self-destruct: Ken, Martin, Lars
75960f20f88dad6bc67892c711c429946063d133stoddard Not self-destruct: BrianP, Ian, Cliff, BillS
75960f20f88dad6bc67892c711c429946063d133stoddard Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd
75960f20f88dad6bc67892c711c429946063d133stoddard /* The below was a concept on *how* to handle the problem */
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddard Have 2 parents: +1: jim
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddard -1: Justin, wrowe, rederpj, nd
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddard +0: Lars, Martin (while standing by, could it do
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddard something useful?)
40a5b7189dbbb28e107bf008ee625f2f0142c2ccdgaudet * Make the worker MPM the default MPM for threaded Unix boxes.
40a5b7189dbbb28e107bf008ee625f2f0142c2ccdgaudet +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd
40a5b7189dbbb28e107bf008ee625f2f0142c2ccdgaudet +0: BrianP, Aaron (mutex contention is looking better with the
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddard latest code, let's continue tuning and testing), rederpj, jim
a5ed555df952c85bc1b179f5981e8a6c54ba16e6stoddardRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
56ca30c968906053ae61acb218420667bb58d996rbb * Patches submitted to the bug database:
56ca30c968906053ae61acb218420667bb58d996rbb http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2.0&keywords=PatchAvailable
56ca30c968906053ae61acb218420667bb58d996rbb * Filter stacks and subrequests, redirects and fast redirects.
70f6f32765cfaadd6da8de6f0fea97ddd72d8fadmanoj There's at least one PR that suffers from the current unclean behaviour
70f6f32765cfaadd6da8de6f0fea97ddd72d8fadmanoj (which lets the server send garbage): PR 17629
70f6f32765cfaadd6da8de6f0fea97ddd72d8fadmanoj nd says: Every subrequest should get its own filter stack with the
56ca30c968906053ae61acb218420667bb58d996rbb subreq_core filter as bottom-most. That filter does two things:
0bff2f28ef945280c17099c142126178a78e1e54manoj - swallow EOS buckets
0bff2f28ef945280c17099c142126178a78e1e54manoj - redirect the data stream to the upper request's (rr->main)
0bff2f28ef945280c17099c142126178a78e1e54manoj filter chain directly after the subrequest's starting
9c09943bad734ebd5c7cc10bd6d63b75c4c6e056stoddard Once we have a clean solution, we can try to optimize
9c09943bad734ebd5c7cc10bd6d63b75c4c6e056stoddard it, so that the server won't be slow down too much.
0bff2f28ef945280c17099c142126178a78e1e54manoj * RFC 2616 violations.
0bff2f28ef945280c17099c142126178a78e1e54manoj Closed PRs: 15857.
0bff2f28ef945280c17099c142126178a78e1e54manoj Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
9c09943bad734ebd5c7cc10bd6d63b75c4c6e056stoddard 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
75960f20f88dad6bc67892c711c429946063d133stoddard 16138, 16139, 16140, 16142, 16518, 16520, 16521,
0bff2f28ef945280c17099c142126178a78e1e54manoj jerenkrantz says: need to decide how many we need to backport and/or
0bff2f28ef945280c17099c142126178a78e1e54manoj if these rise to showstopper status.
9c09943bad734ebd5c7cc10bd6d63b75c4c6e056stoddard wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"
aa1faea36e4ae357bc603a2337b6adc54f5daec1manoj out of this list, without reviewing them individually.
f03d292915be9977eaf74e9be7b0404aec226f84manoj * There is a bug in how we sort some hooks, at least the pre-config
f03d292915be9977eaf74e9be7b0404aec226f84manoj hook. The first time we call the hooks, they are in the correct
3304cbd819df02e7548e9338dc0afa8d3ba29358manoj order, but the second time, we don't sort them correctly. Currently,
f03d292915be9977eaf74e9be7b0404aec226f84manoj the modules/http/config.m4 file has been renamed to
f03d292915be9977eaf74e9be7b0404aec226f84manoj modules/http/config2.m4 to work around this problem, it should moved
f03d292915be9977eaf74e9be7b0404aec226f84manoj back when this is fixed.
aa1faea36e4ae357bc603a2337b6adc54f5daec1manoj OtherBill offers that this is a SERIOUS problem. We do not sort
aa1faea36e4ae357bc603a2337b6adc54f5daec1manoj correctly by the ordering arguments passed to the register hook
aa1faea36e4ae357bc603a2337b6adc54f5daec1manoj functions. This was proven when I reordered the open_logs hook
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj to attempt to open the error logs prior to the access logs. Possibly
302dc1f7b3feee23a91ad8f3cf3cb2edd95a557bmanoj the entire sorting code needs to be refactored.
302dc1f7b3feee23a91ad8f3cf3cb2edd95a557bmanoj * pipes deadlock on all platforms with limited pipe buffers (e.g. both
302dc1f7b3feee23a91ad8f3cf3cb2edd95a557bmanoj Linux and Win32, as opposed to only Win32 on 1.3). The right solution
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)
d5defd5a0c5cdbaf74b85939484dc2b6c8317d19manoj * All handlers should always send content down even if r->header_only
d5defd5a0c5cdbaf74b85939484dc2b6c8317d19manoj is set. If not, it means that the HEAD requests don't generate the
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj same headers as a GET which is wrong.
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj * HP/UX 10.20: compile breakage in APR. Looks like it should be easy
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj to fix, probably just some extraneous #include's that are fouling
0bff2f28ef945280c17099c142126178a78e1e54manoj Jeff: See my reply and patch in the PR (and previous commit to
0bff2f28ef945280c17099c142126178a78e1e54manoj stop using "pipe" as a field name). If patch is committed, we
0bff2f28ef945280c17099c142126178a78e1e54manoj should be okay. I'll wait to see if the user tests the patch.
d6b3cb141f0667101c1bca883ad15b383402c93bfielding Update by Jeff 20020722: I got an account on HP 10.20. It looks
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj like some of the APR thread detection is screwed up. If we find
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj pthread.h but we can't compile the pthread test program we still
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj think we can use threads. For that reason, the patch I posted
40a5b7189dbbb28e107bf008ee625f2f0142c2ccdgaudet to the PR won't work as-is since a failed compile of the test
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj program means nothing.
dbf0c7bef06259486cd2748a2d0e82f27e099d6efielding * exec cmd and suexec arg-passing enhancements
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj Status: Patches proposed
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj (see the "proc.patch" and "suexec-shell.patch" links in this message)
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj * The 2.0.36 worker MPM graceless shutdown changes work but are
f6a6245816cd866361da8c576b1f47c7a54b6610fanf a bit clunky on some platforms; eg, on Linux, the loop to
f6a6245816cd866361da8c576b1f47c7a54b6610fanf join each worker thread seems to hang, and the parent ends up
f6a6245816cd866361da8c576b1f47c7a54b6610fanf killing off the child with SIGKILL. But at least it shuts down.
f6a6245816cd866361da8c576b1f47c7a54b6610fanf * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj * We do not properly substitute the prefix-variables in the configuration
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj scripts or generated-configs. (i.e. if sysconfdir is etc,
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj httpd-std.conf points to conf.)
d6b3cb141f0667101c1bca883ad15b383402c93bfielding * If any request gets through ap_process_request_internal() and is
d6b3cb141f0667101c1bca883ad15b383402c93bfielding scheduled to be served by the core handler, without a flag that this
d6b3cb141f0667101c1bca883ad15b383402c93bfielding r->filename was tested by dir/file_walk, we need to 500 at the very
d6b3cb141f0667101c1bca883ad15b383402c93bfielding end of the ap_process_request_internal() processing so sub_req-esters
d6b3cb141f0667101c1bca883ad15b383402c93bfielding know this request cannot be run. This provides authors of older
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj modules better compatibility, while still improving the security and
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj robustness of 2.0.
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj Status: still need to decide where this goes, OtherBill comments...
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj [Deleted comments regarding the ap_run_handler phase, as irrelevant
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj as BillS points out that "common case will be caught in
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj default_handler already (with the r->finfo.filetype == 0 check)"
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj and the issue is detecting this -before- we try to run the req.]
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj gregames says: can this happen somehow without a broken module
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj being involved? If not, why waste cycles trying to defend against
d6b3cb141f0667101c1bca883ad15b383402c93bfielding potential broken modules? It seems futile.
d6b3cb141f0667101c1bca883ad15b383402c93bfielding wrowe counters: no, it shouldn't happen unless the module is broken.
d6b3cb141f0667101c1bca883ad15b383402c93bfielding But the right answer is to fail the request up-front in dir/file
(see <URL:http://Source-Zone.Org/Apache/regression/>):
extensions. It isn't clear if Set...Filter(s) should be inserted
before or after the Add...Filter(s) which are ordered by sequence of
will require a portable mechanism to pass data and file/socket
ap_unescape_url() in util.c). It's permitted and passed
the child_init hook (i.e. the fcntl lock needs to be resynced).
FreeBSD 5.2-RC is a confirmed fix w/either libkse or libthr.
[libc_r, still the default, does not serve any pages w/worker;
so on FreeBSD 5.2, you must use libmap.conf (see man page).]
libkse/libthr are acceptable. Still not recommended for the
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
* Combine log_child and piped_log_spawn. Clean up http_log.c.
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
tree apr/apr-util, but it's a good start. There's still the
* ssl_engine_pphrase.c needs to be reworked so it is generic enough
* mod_cache: CacheEnable/CacheDisable should accept regular expressions.
* mod_mem_cache/mod_disk_cache: Need to be able to query cache
* Enable mod_cache/mod_mem_cache/mod_disk_cache to handle
* mod_mem_cache/mod_disk_cache: Complete implementing config
PR#1191: setlogin() is not called, causing problems with e.g. identd
PR#1287: add allow,deny/deny,allow warning to mod_access
PR#1117: Using NIS passwd.byname dbm files with AuthDBMUserFile
PR#2873: Feedback/Comment on APACI
PR#2431: A small addition to rotatelogs.c to improve program functionality.
PR#2889: Inclusion of RPM spec file in CVS/distributions
* orig_ct in the byterange/multipart handling may not be