On Wednesday, October 22, 2003, at 04:13 PM, Stas Bekman wrote:
We just try to walk the thin rope of balance and use our common sense
to decide what should be noted and what note, often times noting to
each other when we think that some change log is due or on the
opposite useless.
Works for
flood STATUS: -*-text-*-
Last modified at [$Date: 2003/07/01 20:55:12 $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13,
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2002/03/09 05:22:48 $]
Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
framework failed)
* change existing tests that frob the DocumentRoot (e.g.,
On Mon, 20 Oct 2003 15:54:58 -0400 (EDT)
Norman Tuttle [EMAIL PROTECTED] wrote:
Sorry for jumping in so late, but was out of the net for few weeks...
This patch fixed the following errors in the cookie code in Flood:
(1) Original code only handled a single set-cookie header for a
given HTTP
[EMAIL PROTECTED] wrote:
stas2003/10/21 15:09:11
Modified:perl-framework/Apache-Test/lib/Apache TestConfig.pm
Log:
complete the removal of hardcoding project/lib (besides the autogenerated
t/TEST and other scripts where mp2 build must have it in @INC)
[snip]
+# mp2
Geoffrey Young wrote:
[EMAIL PROTECTED] wrote:
stas2003/10/21 15:09:11
Modified:perl-framework/Apache-Test/lib/Apache TestConfig.pm
Log:
complete the removal of hardcoding project/lib (besides the
autogenerated
t/TEST and other scripts where mp2 build must have it in @INC)
I should have noticed this before, but all the mod_perl foo in
TestConfig really belongs in TestConfigPerl (including the stuff that
was there before this flurry of commits :)
it's too late for 1.05 at this point (which I hope to release on
monday or tuesday) but right afterward I'm going to
Flood developers:
I discovered an error where my system would simply lock up (with maximum
CPU utilization from Flood.exe!) while trying to access an https page,
which is using a server-side certificate, when running Flood from Windows
(did not experience this problem in either Linux. My current
