Re: httpd.conf.in

2002-01-10 Thread Stas Bekman
Rick Myers wrote: Minimal problem description... t/TEST -clean touch t/conf/httpd.conf.in t/TEST -configure grep Include t/conf/httpd.conf Include "/home/rik/dev/Apache/AlterTransChain2/t/conf/extra.conf" Include "/home/rik/dev/Apache/AlterTransChain2/t/conf/httpd.conf" Good catch. committed. Than

httpd.conf.in

2002-01-10 Thread Rick Myers
Minimal problem description... t/TEST -clean touch t/conf/httpd.conf.in t/TEST -configure grep Include t/conf/httpd.conf Include "/home/rik/dev/Apache/AlterTransChain2/t/conf/extra.conf" Include "/home/rik/dev/Apache/AlterTransChain2/t/conf/httpd.conf" Include "/home/rik/dev/Apache/AlterTransChai

Re: cvs commit: httpd-test/perl-framework/t/apache etags.t

2002-01-10 Thread Rodent of Unusual Size
Doug MacEachern wrote: > > well, i said it was incomplete, MMN need to be checked too. I saw that you added it, but I'm not sure how to check it.. > skipping a test based on a 500 response code is bogus if you > ask me. Why? > > The real issue is: why doesn't an invalid .htaccess file cause >

Re: Testing remote server

2002-01-10 Thread Rodent of Unusual Size
Doug MacEachern wrote: > > it does run (and fails) with 2.0. The question is "why"? Why doesn't it get a 500 when it encounters a bogus line in the .htaccess file? I haven't verified it yet; what does the first request say with -v or -d lwp? -- #kenP-)} Ken Coar, Sanagendamgagwedweinini

Re: cvs commit: httpd-test/perl-framework/t/apache etags.t

2002-01-10 Thread Doug MacEachern
On Thu, 10 Jan 2002, Rodent of Unusual Size wrote: > Um, but it's going to work with 2.0. Please revert your patch > because it's broken. The test for a 500 return allows the > test to skip on versions of Apache that don't have the directive > (like 1.3.22). Your change will cause the skip to b

Re: cvs commit: httpd-test/perl-framework/t/apache etags.t

2002-01-10 Thread Rodent of Unusual Size
[EMAIL PROTECTED] wrote: > > this test does not work with 2.0 Um, but it's going to work with 2.0. Please revert your patch because it's broken. The test for a 500 return allows the test to skip on versions of Apache that don't have the directive (like 1.3.22). Your change will cause the ski

Re: Testing remote server

2002-01-10 Thread Doug MacEachern
On Tue, 8 Jan 2002, Rodent of Unusual Size wrote: > That test shouldn't even *run* for 2.0; it should get a 500 > and skip. it does run (and fails) with 2.0. i just changed it to require apache 1.x for the moment, which i just realized isn't good enough. should probably be something like: my