d7759bdad133e1e92fe41aab75dd8c1584eda38cjimAPACHE 2.1 STATUS: -*-text-*-

d7759bdad133e1e92fe41aab75dd8c1584eda38cjimLast modified at [$Date$]

d7759bdad133e1e92fe41aab75dd8c1584eda38cjim

4e191199a0aeab09d78df8f5579e745572e8b7bcwsanchezRelease [NOTE that only Alpha/Beta releases occur in 2.1 development]:

f3a5934ca0fb0f0f813bd9d9d06af8937e3f401fjim

f3a5934ca0fb0f0f813bd9d9d06af8937e3f401fjim 2.1.3 : in development

d7759bdad133e1e92fe41aab75dd8c1584eda38cjim 2.1.2 : Released on 12/08/2004 as alpha.

d7759bdad133e1e92fe41aab75dd8c1584eda38cjim 2.1.1 : Released on 11/19/2004 as alpha.

d7759bdad133e1e92fe41aab75dd8c1584eda38cjim 2.1.0 : not released.

d7759bdad133e1e92fe41aab75dd8c1584eda38cjim

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianhPlease consult the following STATUS files for information

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianhon related projects:

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianh

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianh * srclib/apr/STATUS

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianh * srclib/apr-util/STATUS

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianh * docs/STATUS

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianh

b3155b9e3b06b20030ec6c16d98f8dabf12ead9cianhContributors looking for a mission:

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh * Just do an egrep on "TODO" or "XXX" in the source.

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh * Review the "PatchAvailable" bugs in the bug database.

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh Append a comment saying "Reviewed and tested".

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh * Open bugs in the bug database.

ff1234e45aca1b8171d711ecb87f58b9d9100a99ianh

b999f6ba2a266bf9a92687f31bb7e76021ac5891ianhCURRENT RELEASE NOTES:

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwroweRELEASE SHOWSTOPPERS:

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe * Handling of non-trailing / config by non-default handler is broken

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105451701628081&w=2

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe jerenkrantz asks: Why should this block a release?

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe * the edge connection filter cannot be removed

b999f6ba2a266bf9a92687f31bb7e76021ac5891ianh http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=105366252619530&w=2

2ceedfca3a2fdfdb5ff60ca17f030ce91f6331cbwrowe jerenkrantz asks: Why should this block a release?

b999f6ba2a266bf9a92687f31bb7e76021ac5891ianh

7d7931c1f4d46b041ad2ad6fdb9499289063611eianh * Replace proxy handling of request bodies with something which doesn't

1f3a44f2fd7f9fee00b80c7ddcf1028ea145f91drbb gobble up arbitrary amounts of memory. See proxy_http.c in

b9b69856aec9ea58ea1b1e5aff669e8eaf2ebce4rbb proxy-reqbody branch for new implementation.

b9b69856aec9ea58ea1b1e5aff669e8eaf2ebce4rbb

b9b69856aec9ea58ea1b1e5aff669e8eaf2ebce4rbbCURRENT VOTES:

1f3a44f2fd7f9fee00b80c7ddcf1028ea145f91drbb

1f3a44f2fd7f9fee00b80c7ddcf1028ea145f91drbb * httpd-std.conf and friends

1f3a44f2fd7f9fee00b80c7ddcf1028ea145f91drbb

7d7931c1f4d46b041ad2ad6fdb9499289063611eianh a) httpd-std.conf should be tailored by install (from src or

1f3a44f2fd7f9fee00b80c7ddcf1028ea145f91drbb binbuild) even if user has existing httpd.conf

68bcde9c52e9e749482df2800dbdff09559115e0chuck +1: trawick, slive, gregames, ianh, Ken, wrowe, jwoolley, jim, nd,

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck erikabele

43ea154f46345c9722c2b25b2b9f5086ec79eaeeorlikowski wrowe - prefer httpd.default.conf to avoid ambiguity with cvs

43ea154f46345c9722c2b25b2b9f5086ec79eaeeorlikowski

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck b) tailored httpd-std.conf should be copied by install to

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck sysconfdir/examples

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck -0: striker

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck c) tailored httpd-std.conf should be installed to

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck sysconfdir/examples or manualdir/exampleconf/

68bcde9c52e9e749482df2800dbdff09559115e0chuck +1: slive, trawick, Ken, nd (prefer the latter), erikabele

53c2eb831bfe47860e3f5ec9190b15cb92f15181chuck

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck d) Installing a set of default config files when upgrading a server

53c2eb831bfe47860e3f5ec9190b15cb92f15181chuck doesn't make ANY sense at all.

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski +1: ianh - medium/big sites don't use 'standard config' anyway, as it

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski usually needs major customizations

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski -1: Ken, wrowe, jwoolley, jim, nd, erikabele

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski wrowe - diff is wonderful when comparing old/new default configs,

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski even for customized sites that ianh mentions

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski jim - ... assuming that the default configs have been updated

c1635d9f723f28fed4b95e5d9693e554a79e8d77orlikowski with the required inline docs to explain the

4f7dd0949d92462a8adc31eee8aff266eea55204chuck changes

4f7dd0949d92462a8adc31eee8aff266eea55204chuck

4f7dd0949d92462a8adc31eee8aff266eea55204chuck * If the parent process dies, should the remaining child processes

4f7dd0949d92462a8adc31eee8aff266eea55204chuck "gracefully" self-terminate. Or maybe we should make it a runtime

4f7dd0949d92462a8adc31eee8aff266eea55204chuck option, or have a concept of 2 parent processes (one being a

75b3ed55173b29dbdf9e2fb6ec5462bfceee21aechuck "hot spare").

75b3ed55173b29dbdf9e2fb6ec5462bfceee21aechuck See: Message-ID: <3C58232C.FE91F19F@Golux.Com>

75b3ed55173b29dbdf9e2fb6ec5462bfceee21aechuck

4f7dd0949d92462a8adc31eee8aff266eea55204chuck Self-destruct: Ken, Martin, Lars

75b3ed55173b29dbdf9e2fb6ec5462bfceee21aechuck Not self-destruct: BrianP, Ian, Cliff, BillS

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck Make it runtime configurable: Aaron, jim, Justin, wrowe, rederpj, nd

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck /* The below was a concept on *how* to handle the problem */

68bcde9c52e9e749482df2800dbdff09559115e0chuck Have 2 parents: +1: jim

68bcde9c52e9e749482df2800dbdff09559115e0chuck -1: Justin, wrowe, rederpj, nd

68bcde9c52e9e749482df2800dbdff09559115e0chuck +0: Lars, Martin (while standing by, could it do

68bcde9c52e9e749482df2800dbdff09559115e0chuck something useful?)

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Make the worker MPM the default MPM for threaded Unix boxes.

68bcde9c52e9e749482df2800dbdff09559115e0chuck +1: Justin, Ian, Cliff, BillS, striker, wrowe, nd

68bcde9c52e9e749482df2800dbdff09559115e0chuck +0: BrianP, Aaron (mutex contention is looking better with the

68bcde9c52e9e749482df2800dbdff09559115e0chuck latest code, let's continue tuning and testing), rederpj, jim

68bcde9c52e9e749482df2800dbdff09559115e0chuck -0: Lars

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck pquerna: Do we want to change this for 2.2?

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuckRELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Patches submitted to the bug database:

68bcde9c52e9e749482df2800dbdff09559115e0chuck http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-2.0&keywords=PatchAvailable

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * The Event MPM does not work on Solaris 10. Solaris 10 does support the

68bcde9c52e9e749482df2800dbdff09559115e0chuck Threadsafe Pollsets required by the Event MPM, but it does not support

68bcde9c52e9e749482df2800dbdff09559115e0chuck multiple threads calling accept() at the same time. The current

68bcde9c52e9e749482df2800dbdff09559115e0chuck structure of the Event MPM makes adding accept() locking difficult.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Filter stacks and subrequests, redirects and fast redirects.

68bcde9c52e9e749482df2800dbdff09559115e0chuck There's at least one PR that suffers from the current unclean behaviour

68bcde9c52e9e749482df2800dbdff09559115e0chuck (which lets the server send garbage): PR 17629

68bcde9c52e9e749482df2800dbdff09559115e0chuck nd says: Every subrequest should get its own filter stack with the

68bcde9c52e9e749482df2800dbdff09559115e0chuck subreq_core filter as bottom-most. That filter does two things:

68bcde9c52e9e749482df2800dbdff09559115e0chuck - swallow EOS buckets

68bcde9c52e9e749482df2800dbdff09559115e0chuck - redirect the data stream to the upper request's (rr->main)

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck filter chain directly after the subrequest's starting

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck point.

68bcde9c52e9e749482df2800dbdff09559115e0chuck Once we have a clean solution, we can try to optimize

68bcde9c52e9e749482df2800dbdff09559115e0chuck it, so that the server won't be slow down too much.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * RFC 2616 violations.

68bcde9c52e9e749482df2800dbdff09559115e0chuck Closed PRs: 15857.

68bcde9c52e9e749482df2800dbdff09559115e0chuck Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,

68bcde9c52e9e749482df2800dbdff09559115e0chuck 15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,

68bcde9c52e9e749482df2800dbdff09559115e0chuck 16138, 16139, 16140, 16142, 16518, 16520, 16521,

68bcde9c52e9e749482df2800dbdff09559115e0chuck jerenkrantz says: need to decide how many we need to backport and/or

68bcde9c52e9e749482df2800dbdff09559115e0chuck if these rise to showstopper status.

68bcde9c52e9e749482df2800dbdff09559115e0chuck wrowe suggests: it would be nice to see "MUST" v.s. "SHOULD" v.s. "MAY"

68bcde9c52e9e749482df2800dbdff09559115e0chuck out of this list, without reviewing them individually.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * There is a bug in how we sort some hooks, at least the pre-config

68bcde9c52e9e749482df2800dbdff09559115e0chuck hook. The first time we call the hooks, they are in the correct

68bcde9c52e9e749482df2800dbdff09559115e0chuck order, but the second time, we don't sort them correctly. Currently,

68bcde9c52e9e749482df2800dbdff09559115e0chuck the modules/http/config.m4 file has been renamed to

68bcde9c52e9e749482df2800dbdff09559115e0chuck modules/http/config2.m4 to work around this problem, it should moved

68bcde9c52e9e749482df2800dbdff09559115e0chuck back when this is fixed.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck OtherBill offers that this is a SERIOUS problem. We do not sort

68bcde9c52e9e749482df2800dbdff09559115e0chuck correctly by the ordering arguments passed to the register hook

68bcde9c52e9e749482df2800dbdff09559115e0chuck functions. This was proven when I reordered the open_logs hook

68bcde9c52e9e749482df2800dbdff09559115e0chuck to attempt to open the error logs prior to the access logs. Possibly

68bcde9c52e9e749482df2800dbdff09559115e0chuck the entire sorting code needs to be refactored.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck * pipes deadlock on all platforms with limited pipe buffers (e.g. both

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck Linux and Win32, as opposed to only Win32 on 1.3). The right solution

68bcde9c52e9e749482df2800dbdff09559115e0chuck is either GStein's proposal for a "CGI Brigade", or OtherBill's proposal

68bcde9c52e9e749482df2800dbdff09559115e0chuck for "Poll Buckets" for "Polling Filter Chains". Or maybe both :-)

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * All handlers should always send content down even if r->header_only

68bcde9c52e9e749482df2800dbdff09559115e0chuck is set. If not, it means that the HEAD requests don't generate the

68bcde9c52e9e749482df2800dbdff09559115e0chuck same headers as a GET which is wrong.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * exec cmd and suexec arg-passing enhancements

68bcde9c52e9e749482df2800dbdff09559115e0chuck Status: Patches proposed

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <20020526041748.A29148@prodigy.Redbrick.DCU.IE>

68bcde9c52e9e749482df2800dbdff09559115e0chuck (see the "proc.patch" and "suexec-shell.patch" links in this message)

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * The 2.0.36 worker MPM graceless shutdown changes work but are

68bcde9c52e9e749482df2800dbdff09559115e0chuck a bit clunky on some platforms; eg, on Linux, the loop to

68bcde9c52e9e749482df2800dbdff09559115e0chuck join each worker thread seems to hang, and the parent ends up

68bcde9c52e9e749482df2800dbdff09559115e0chuck killing off the child with SIGKILL. But at least it shuts down.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck * --enable-mods-shared="foo1 foo2" is busted on Darwin. Pier

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * We do not properly substitute the prefix-variables in the configuration

68bcde9c52e9e749482df2800dbdff09559115e0chuck scripts or generated-configs. (i.e. if sysconfdir is etc,

68bcde9c52e9e749482df2800dbdff09559115e0chuck httpd-std.conf points to conf.)

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * If any request gets through ap_process_request_internal() and is

68bcde9c52e9e749482df2800dbdff09559115e0chuck scheduled to be served by the core handler, without a flag that this

68bcde9c52e9e749482df2800dbdff09559115e0chuck r->filename was tested by dir/file_walk, we need to 500 at the very

68bcde9c52e9e749482df2800dbdff09559115e0chuck end of the ap_process_request_internal() processing so sub_req-esters

68bcde9c52e9e749482df2800dbdff09559115e0chuck know this request cannot be run. This provides authors of older

68bcde9c52e9e749482df2800dbdff09559115e0chuck modules better compatibility, while still improving the security and

68bcde9c52e9e749482df2800dbdff09559115e0chuck robustness of 2.0.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck Status: still need to decide where this goes, OtherBill comments...

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>

68bcde9c52e9e749482df2800dbdff09559115e0chuck [Deleted comments regarding the ap_run_handler phase, as irrelevant

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck as BillS points out that "common case will be caught in

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck default_handler already (with the r->finfo.filetype == 0 check)"

68bcde9c52e9e749482df2800dbdff09559115e0chuck and the issue is detecting this -before- we try to run the req.]

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck gregames says: can this happen somehow without a broken module

68bcde9c52e9e749482df2800dbdff09559115e0chuck being involved? If not, why waste cycles trying to defend against

68bcde9c52e9e749482df2800dbdff09559115e0chuck potential broken modules? It seems futile.

68bcde9c52e9e749482df2800dbdff09559115e0chuck wrowe counters: no, it shouldn't happen unless the module is broken.

68bcde9c52e9e749482df2800dbdff09559115e0chuck But the right answer is to fail the request up-front in dir/file

68bcde9c52e9e749482df2800dbdff09559115e0chuck walk if the path was entirely invalid; and we can't do that either

68bcde9c52e9e749482df2800dbdff09559115e0chuck UNTIL 2.1 or we break modules that haven't hooked map_to_storage.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me

68bcde9c52e9e749482df2800dbdff09559115e0chuck how the Perchild MPM should be re-written. It hasn't worked

68bcde9c52e9e749482df2800dbdff09559115e0chuck correctly since filters were added because it wasn't possible to

68bcde9c52e9e749482df2800dbdff09559115e0chuck get the content that had already been written and the socket at

68bcde9c52e9e749482df2800dbdff09559115e0chuck the same time. This mode lets us do that, so the MPM can be

68bcde9c52e9e749482df2800dbdff09559115e0chuck fixed.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Can a static httpd be built reliably?

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <20020207142751.T31582@clove.org>

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Usage of APR_BRIGADE_NORMALIZE in core_input_filter should be

68bcde9c52e9e749482df2800dbdff09559115e0chuck removed if possible.

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <Pine.LNX.4.33.0201202232430.318-100000@deepthought.cs.virginia.edu>

68bcde9c52e9e749482df2800dbdff09559115e0chuck Jeff wonders if we still care about this. It is no longer an

68bcde9c52e9e749482df2800dbdff09559115e0chuck API issue but simply an extra trip through the brigade.

68bcde9c52e9e749482df2800dbdff09559115e0chuck

68bcde9c52e9e749482df2800dbdff09559115e0chuck * Get perchild to work on platforms other than Linux. This

68bcde9c52e9e749482df2800dbdff09559115e0chuck will require a portable mechanism to pass data and file/socket

68bcde9c52e9e749482df2800dbdff09559115e0chuck descriptors between vhost child groups. An API was proposed

68bcde9c52e9e749482df2800dbdff09559115e0chuck on dev@apr:

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <20020111115006.K1529@clove.org>

68bcde9c52e9e749482df2800dbdff09559115e0chuck

0c233c76f21b358f4a0d81e0f956339ca727c14cchuck * Try to get libtool inter-library dependency code working on AIX.

68bcde9c52e9e749482df2800dbdff09559115e0chuck Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>

68bcde9c52e9e749482df2800dbdff09559115e0chuck

4f7dd0949d92462a8adc31eee8aff266eea55204chuck Justin says: If we get it working on AIX, we can enable this

4f7dd0949d92462a8adc31eee8aff266eea55204chuck on all platforms and clean up our build system

68bcde9c52e9e749482df2800dbdff09559115e0chuck somewhat.

4f7dd0949d92462a8adc31eee8aff266eea55204chuck Jeff says: I thought I tested a patch for you sometime in

4f7dd0949d92462a8adc31eee8aff266eea55204chuck January that you were going to commit within a few

68bcde9c52e9e749482df2800dbdff09559115e0chuck days.

4f7dd0949d92462a8adc31eee8aff266eea55204chuck

4f7dd0949d92462a8adc31eee8aff266eea55204chuck * Handling of %2f in URIs. Currently both 1.3 and 2.0

68bcde9c52e9e749482df2800dbdff09559115e0chuck 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.

OtherBill adds that %2f as the SECOND character of a multibyte

sequence causes the request to fail! This happens notably in

the ja-jis encoding.

* 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.

Status: Works with FreeBSD 5.3. Does not work in previous versions.

This has also been reported on Cygwin.

* 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?

On the other hand, 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.

* 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)

* Win32: Get Apache working on Windows 95/98. The following work

(at least) needs to be done:

- Document warning that OSR2 is required (for Crypt functions, in

rand.c, at least.) This could be resolved with an SSL library, or

randomization in APR itself.

- Bring the Win9xConHook.dll from 1.3 into 2.0 (no sense till it

actually works) and add in a splash of Win9x service code.

* Fix the worker MPM to use POD to kill child processes instead

of ap_os_killpg, regardless of how they should die.

* 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>

* When sufficiently tested, the AllowEncodedSlashes/%2f patch

needs to be backported to 2.0 and 1.3.

* 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

gstein: agreed. apxs should deprecate the -q flag

TODO ISSUES REMAINING IN MOD_SSL:

* In order to use a DSO version of mod_ssl we have to link with

-lssl and -lcrypto. A workaround is in place right now where the

entire EXTRA_LIBS macro is being appended to the objects list, but

this is a hack. We should either revamp the APACHE_CHECK_SSL_TOOLKIT

autoconf function or come up with some other autoconf checks to

search for libssl and libcrypto and properly add them to mod_ssl's

link flags.

* SSL renegotiations in combination with POST request

* Port or dispose all code inside #if 0...#endif blocks that remain

from the porting effort.

* 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

* the shmcb code should just align its memory segment rather than

jumping through all the "safe" memcpy and memset hoops

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_cache: Fix dependency on ATOMIC operators. Need

APR_HAS_ATOMIC_* feature macros.

jerenkrantz says: APR 1.0+ has some guaranteed form of atomics.

* 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.

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.

Other bugs that need fixing:

* ap_discard_request should be converted to use the bucket API

directly rather than waste cycles copying buffers with the old API.

* 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 :-)

Binaries (probably not till beta):

Platform Avail. Volunteer

------------------------------------------------------------------

AIX 4.3.3 no Bill Stoddard

Mandrake 8.1 no open

FreeBSD 4.1 no open

hppa2.0w-hp-hpux11.00 no Cliff Woolley

i386-pc-solaris2.8 no Aaron Bannert

i386-unknown-freebsd4.5 no

i386-unknown-freebsd4.6 no Cliff Woolley

i686-pc-linux-gnu-slackware81 no Cliff Woolley

i686-pc-linux-gnu-rh70 no Aaron Bannert

i686-pc-linux-gnu-rh73 no Cliff Woolley

ia64-hp-hpux11.20 no

powerpc-apple-darwin5.5 no Aaron Bannert

powerpc-unknown-linux-gnu no Graham Leggett

s390-ibm-linux no Greg Ames

sparc-sun-solaris2.8 no Jim Jagielski

NetWare no Brad Nicholes

OS/2 no Brian Havard

OS/390 no Greg Ames

Win32-x86 no William Rowe