jim 98/05/02 17:44:07
Modified: . STATUS
Log:
Update STATUS with a date and some issues
Revision Changes Path
1.348 +7 -18 apache-1.3/STATUS
Index: STATUS
===================================================================
RCS file: /export/home/cvs/apache-1.3/STATUS,v
retrieving revision 1.347
retrieving revision 1.348
diff -u -r1.347 -r1.348
--- STATUS 1998/05/02 11:15:06 1.347
+++ STATUS 1998/05/03 00:44:06 1.348
@@ -5,7 +5,7 @@
1.3.0: Shoot for May 16, 1998 Release!
Brian to be RM, Jim will do announcements
- 1.3b7: In development
+ 1.3b7: In development... Possible release May 8.
1.3b6: Tagged APACHE_1_3b6. Announced and Released 4/20/98
@@ -82,6 +82,10 @@
Available Patches:
+ * Michael Anderson's <[EMAIL PROTECTED]> C++ friendly patch
+ <[EMAIL PROTECTED]>
+ Status: Ben, Jim +1
+
* Arnt Gulbrandsen <[EMAIL PROTECTED]> 03 Apr 1998 21:28:17 +0200
<[EMAIL PROTECTED]> mod_usertrack.c patch:
The patch provides per-domain cookies (which I use to share user-ids
@@ -109,10 +113,7 @@
FINAL RELEASE SHOWSTOPPERS:
* MIME type case sensitivity disparity between 1.2.6 and 1.3b6 (PR #2112)
- Jim: Is the suggested change in find_title() not
- sufficient? Or is the fix to remap all mimes to lowercase?
- Dean: all mime types are already lowercase everywhere else in the
- server
+ mod_autoindex should lowercase the mime-type when comparing
* proxy security fixes from 1.2.5 need to be brought forward
Jim: What are these?
@@ -129,19 +130,7 @@
make the child exit with a special code when a fatal error occurs; the
parent would then abort. See
<[EMAIL PROTECTED]>
- Jim: Is this something to hold 1.3.0 up for? I'm thinking maybe
- some sort of error-code be placed in scoreboard that
- the parent could act on? Of course, we already use
- waitpid() so we have the status already...
- Some of these "we should stop errors" are kinda obvious,
- like a bad lockfile... some I would have no idea.
- I'll generate a list of what I think are these Abort
- errors and ask for feedback.
- Dean: Yep. It's a serious reliability difference between 1.2 and
- 1.3 -- for some errors, such as the bogus group id, 1.2 would
- have exited immediately. 1.3 will consume all system resources,
- it will spawn 32 children per second, and every one of them will
- write a log entry. Besides it's an easy fix.
+ Jim: Possible patch: <[EMAIL PROTECTED]>
* The DoS issue about symlinks to /dev/zero is still present.
A device checker patch had been sent to the list a while ago.
