From: Cliff Woolley Date: Fri, 19 Apr 2002 23:31:35 +0000 (+0000) Subject: showstoppers--; X-Git-Tag: 2.0.36~136 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=94734ed722649e3095e88e0d371eb14eaaee3ece;p=thirdparty%2Fapache%2Fhttpd.git showstoppers--; showstoppers+=2; :-( ...but these might have already been fixed, I just never got a response on-list about them and wanted to note them somewhere where they wouldn't be forgotten git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@94731 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/STATUS b/STATUS index 30b5f3c52b7..f48740ce9c7 100644 --- a/STATUS +++ b/STATUS @@ -1,5 +1,5 @@ APACHE 2.0 STATUS: -*-text-*- -Last modified at [$Date: 2002/04/19 18:21:45 $] +Last modified at [$Date: 2002/04/19 23:31:35 $] Release: @@ -49,8 +49,12 @@ CURRENT RELEASE NOTES: RELEASE SHOWSTOPPERS: - * Daedalus segfaults with 2.0.35 - Greg and Cliff are working on this. + * Did daedalus's 416 problems get fixed? Greg, I think you had a patch, + but did it get committed? Is there still a known condition (related + to this or not) that will cause the byterange filter to segv? + + * Is the 416 problem different from the C-L / byterange filter + misordering problem? If not, is this one fixed? * worker MPM segfaults because the apr_bucket_alloc_t is cleaned up twice.