Re: 2.0.28 results, need interpretation

2001-11-13 Thread Rodent of Unusual Size
Doug MacEachern wrote:
> 
> On Tue, 13 Nov 2001, Aaron Bannert wrote:
> 
> > The limits failure has to with LimitRequestBody, and looks
> > to be a known issue (see modules/http/http_protocol.c:1314,
> > "/* XXX shouldn't we enforce this for chunked encoding too? */").
> > But you probably already knew this. :)
> 
> ken told me he wasn't surprised that test is failing with 2.0,
> but didn't say why.

The test is correctly identifying the fact that the Apache code
is broken.  See the recent discussions about LimitRequest*
on the [EMAIL PROTECTED] list.  I'm not currently in a position to
look into it more closely.
-- 
#kenP-)}

Ken Coar, Sanagendamgagwedweinini  http://Golux.Com/coar/
Author, developer, opinionist  http://Apache-Server.Com/

"All right everyone!  Step away from the glowing hamburger!"


Re: 2.0.28 results, need interpretation

2001-11-13 Thread Aaron Bannert
On Tue, Nov 13, 2001 at 10:34:35AM -0800, Doug MacEachern wrote:
> this is fixed now.

Works great, thanks.

-aaron


Re: 2.0.28 results, need interpretation

2001-11-13 Thread Doug MacEachern
On Tue, 13 Nov 2001, Aaron Bannert wrote:
 
> The limits failure has to with LimitRequestBody, and looks to be a known
> issue (see modules/http/http_protocol.c:1314, "/* XXX shouldn't we enforce
> this for chunked encoding too? */"). But you probably already knew this. :)

ken told me he wasn't surprised that test is failing with 2.0, but didn't
say why.
 
> As for the cgi error, is this the error that Cliff reported earlier? It
> looks like it's a simple error with how @CGI_MODULE@ is being replaced
> in t/conf/extra.conf.in on about line 175. In my setup, no matter what
> I do it gets replaced with mod_cgi.c, which means those directives are
> never included with worker's mod_cgid.c. Can someone with more experience
> with perl voodoo check this out and let me know what I'm doing wrong here?

this is fixed now.




2.0.28 results, need interpretation

2001-11-13 Thread Aaron Bannert
I'm fairly new to the perl-framework testing harness, and I'm getting
some results I'm not sure how to interpret on my Solaris 8 build of
the rolled 2.0.28 tarball.

With the worker MPM (with --enable-cgid) I get:

Failed Test Status Wstat Total Fail  Failed  List of Failed
apache/limits.t
   101  10.00%  9
modules/cgi.t 36   33  91.67%  1-4, 6, 8-27, 29-36

But on prefork with the same build parameters (s/cgid/cgi of course) I get
only:

Failed Test Status Wstat Total Fail  Failed  List of Failed
apache/limits.t
   101  10.00%  9


The limits failure has to with LimitRequestBody, and looks to be a known
issue (see modules/http/http_protocol.c:1314, "/* XXX shouldn't we enforce
this for chunked encoding too? */"). But you probably already knew this. :)

As for the cgi error, is this the error that Cliff reported earlier? It
looks like it's a simple error with how @CGI_MODULE@ is being replaced
in t/conf/extra.conf.in on about line 175. In my setup, no matter what
I do it gets replaced with mod_cgi.c, which means those directives are
never included with worker's mod_cgid.c. Can someone with more experience
with perl voodoo check this out and let me know what I'm doing wrong here?

-aaron

p.s. Solaris 8 intel (07/'01 update), perl 5.6.1