APACHE 2.0 STATUS: -*-text-*-
-Last modified at [$Date: 2002/02/21 18:56:15 $]
+Last modified at [$Date: 2002/03/26 20:35:50 $]
Release:
- 2.0.33 : in development
- 2.0.32 : released Feburary 16, 2002.
+ 2.0.34 : tagged March 26, 2002.
+ 2.0.33 : tagged March 6, 2002. not released.
+ 2.0.32 : released Feburary 16, 2002 as beta.
2.0.31 : rolled Feburary 1, 2002. not released.
2.0.30 : tagged January 8, 2002. not rolled.
2.0.29 : tagged November 27, 2001. not rolled.
- 2.0.28 : released November 13, 2001
+ 2.0.28 : released November 13, 2001 as beta.
2.0.27 : rolled November 6, 2001
2.0.26 : tagged October 16, 2001. not rolled.
2.0.25 : rolled August 29, 2001
CURRENT RELEASE NOTES:
- * 32 status: Released as beta. Enjoy.
+ * 34 status: Let's get all API changes and showstoppers in this one.
+ Please.
FINAL RELEASE SHOWSTOPPERS:
- * All ap_internal_fast_redirect()ed requests are losing their filters
- and output headers. mod_negotiation derived Multiviewed documents
- and mod_dir DirectoryIndex documents both demonstrate this behavior.
- cf reply: <007c01c1b3d1$46714650$94c0b0d0@v505>
- to thread: <200202121332.IAA27467@web.turner.com>
- Solutions:
- Ditch fast_redirect, it was bogus in 1.3 and it's bogus now.
- In Agreement? : Justin
- Fix [and *Maintain*] fast_redirect, it was useful to our redirects
- in negotiation and dir, and it's useful to 3rd parties.
- In Agreement? :
-
- * 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
- authors of older modules better compatibility, while still improving
- the security and robustness of 2.0.
- Status: still need to decide where this goes, OtherBill comments...
- Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
- we need to look at halting this in the 'default handler' case,
- and that implies pushing the 'handler election' into the request
- internal processing phase from the run request phase.
-
- * 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.
- BrianP asks: "Is this really a showstopper?"
- IanH says: "If we don't do it before we go live we will have 2
- different API's to support in APR"
- BrianP agrees: "Yes, let's clean up the remaining dependencies
- on the old lock API."
-
- * We need to find out the right place to add the AddOutputFilterByType
- directive. mod_mime? No. core with fixups? That's what it is now.
- ap_pass_brigade() hook? As a filter that runs at HTTP_HEADER stage?
- This needs to be resolved before the next public release.
- Message-ID: <018701c1b99c$f0f24310$0a01230a@KOJ>
-
* API changes planned for 2.0 that should happen before the
GA release:
* Free lists for bucket allocation
+ * We do not properly substitute the prefix-variables in the configuration
+ scripts or generated-configs. (i.e. if sysconfdir is etc,
+ httpd-std.conf points to conf.)
+ Aaron says: This is not a showstopper, these problems have existed
+ for as long as I can remember. It would be nice to fix
+ them but they are not new.
+ Not a showstopper: Jeff, Aaron, BillS, gregames
+
CURRENT VOTES:
- * Should we always build binaries statically unless otherwise
+ * Should we always build [support*] binaries statically unless otherwise
indicated?
Message-ID: <20020129210006.B23512@Lithium.MeepZor.Com>
- +1: Ken
+ +1: Ken, *wrowe [they are PITAs on OSX]
-1: Justin, Ian
* If the parent process dies, should the remaining child processes
Not self-destruct: BrianP, Ian, Cliff, BillS
Make it runtime configurable: Aaron, Jim, Justin
Have 2 parents: +1: Jim
- -1: Justin
+ -1: Justin, wrowe [for 2.0]
+0: Martin (while standing by, could it do
something useful?)
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
+ * If any request gets through ap_process_request_internal() and is
+ scheduled to be served by 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 so sub_req-esters
+ know this request cannot be run. This provides authors of older
+ modules better compatibility, while still improving the security and
+ robustness of 2.0.
+
+ Status: still need to decide where this goes, OtherBill comments...
+ Message-ID: <065701c14526$495203b0$96c0b0d0@roweclan.net>
+ [Deleted comments regarding the ap_run_handler phase, as irrelevant
+ as BillS points out that "common case will be caught in
+ default_handler already (with the r->finfo.filetype == 0 check)"
+ and the issue is detecting this -before- we try to run the req.]
+
+ gregames says: can this happen somehow without a broken module
+ being involved? If not, why waste cycles trying to defend against
+ potential broken modules? It seems futile.
+ wrowe counters: no, it shouldn't happen unless the module is broken.
+ But the right answer is to fail the request up-front in dir/file
+ walk if the path was entirely invalid; and we can't do that either
+ or we break modules that are unwilling to hook map_to_storage.
+
+ * Rewrite core_output_filter. It is nearly impossible to support
+ it with predictable results as it is implemented now.
+
+ * Convert all instances of the old apr_lock_t type to the new
+ types.
+ Status: Aaron has converted all but the perchild MPM to
+ use the new lock API. Since perchild has been put
+ on the back burner, this is no longer a showstopper.
+ Aaron will patch perchild as soon as it becomes
+ buildable again.
+
+ * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me
+ how the Perchild MPM should be re-written. It hasn't worked
+ correctly since filters were added because it wasn't possible to
+ get the content that had already been written and the socket at
+ the same time. This mode lets us do that, so the MPM can be
+ fixed.
+
* htpasswd blindly processes the file you give it, and does no
sanity checking before totally corrupting whatever file it was
you thought you had. It should check the input file and bail
on dev@apr:
Message-ID: <20020111115006.K1529@clove.org>
- * Recent changes to ap_rgetline may have broken EBCDIC boxes.
- Message-ID: <20020122072605.GF28051@ebuilt.com>
- Justin says: "I don't have an EBCDIC box to test on. A potential
- solution is to split out ap_rgetline into two
- functions as described in this message."
- gregames says: I see the breakage now, and volunteer to fix it
- when things calm down a little. It looks OK when
- there are complete lines and no mime continuations.
-
* CGI single-byte reads
BrianP suggests that this is caused by the ap_scan_script_header_err()
routine, which will do single-byte reads until it finds the end
to read from.
Proposed solution in:
Message-ID: <3C36ADAF.60601@cnet.com>
+ Update 3/23/2002: solution implemented for mod_cgi, mod_cgid remains
+ to be fixed
* Try to get libtool inter-library dependency code working on AIX.
Message-ID: <cm3n10lx555.fsf@rdu163-40-092.nc.rr.com>
stoddard: Not fixed. 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.
* Win32: Add a simple hold console open patch (wait for close or
the ESC key, with a nice message) if the server died a bad
The current porting state is summarized in modules/ssl/README. The
remaining work includes:
(1) stablizing/optimizing the SSL filter logic
- (2) Enabling the various SSL caching mechanisms (shmcb, shmht)
- (3) Enabling SSL extentions
- (4) Trying to seperate the https filter logic from mod_ssl -
+ (2) Enabling SSL extentions
+ (3) Trying to seperate the https filter logic from mod_ssl -
This is to facilitate other modules that wish to use the https
filter or the mod_ssl logic or both as required.
- Justin: mod_ssl filter logic is redone, so that should be fine.
- Madhu has submitted a patch for SSL caching - however, I
- am -0 on that patch as I *think* we could implement the
- shared memory another way that is much cleaner (i.e.
- treat shmem directly as a dbm via APR routines). Justin
- also thinks that the https filter logic may be sufficiently
- decoupled now, but isn't really sure.
* Performance & Debug: Eliminate most (and perhaps all) of the
malloc/free calls in the bucket brigade code. Need some
have something to look at/compare with.
* Eliminate unnecessary creation of pipes in mod_cgid
- Status: Ken asks, didn't Jeff fix this when he fixed the queue
- overrun?
-
- * the autoconf setup should be fixed to default to using the
- "Apache" layout from config.layout, and each variable settable
- in a layout should be overridable on the command line. Plus,
- what we do right now just doesn't seem to fully fit into how autoconf
- works, eg. AC_PREFIX_DEFAULT issues.
- Message-ID: <Pine.BSF.4.20.0104031557420.20876-100000@alive.znep.com>
* Combine log_child and piped_log_spawn. Clean up http_log.c.
Common logging API.
* Win32: Get Apache working on Windows 95/98. The following work
(at least) needs to be done:
- - winnt MPM: Fix 95/98 code paths in the winnt MPM. There is some NT
- specific code that is still not in NT only code paths
- - IOL binds to APR sendfile, implemented with TransmitFile, which
- is not available on 95/98.
- 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.
* Fix the worker MPM to use POD to kill child processes instead
of ap_os_killpg, regardless of how they should die. (Ryan Bloom)
+ * mod_cache: handle cache_control: no_cache "field_name" to enable
+ cacheing the response w/o header "field_name"
+ See RFC2616 section 14.9.1
+
+ * 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>
+
PRs that have been suspended forever waiting for someone to
put them into 'the next release':
projects / apache / blobdiff