Dear PayPal user, As part of our security measures, we regularly screen activity in the PayPal system. We recently contacted you after noticing an issue on your account. We requested information from you for the following reason: We recently received a report of unauthorized credit card use associated with this account. As a precaution, we have limited access to your PayPal account in order to protect against future unauthorized transactions. Case ID Number: PP-503-410-563 This is a reminder to restore your account as soon as possible. Please download the form attached to this email and open it in a web browser. Once opened, you will be provided with steps to restore your account access. We appreciate your understanding as we work to ensure account safety. In accordance with PayPal's User Agreement, your account access will remain limited until the issue has been resolved. Unfortunately, if access to your account remains limited for an extended period of time, it may result in further limitations or eventual account closure. We encourage you to restore your PayPal account as soon as possible to help avoid this. We thank you for your prompt attention to this matter. Please understand that this is a security measure intended to help protect you and your account. We apologize for any inconvenience. Sincerely, PayPal Account Review Department PayPal Email ID PP638
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td bgcolor="#006600"><center><a href="http://magazinchasoff.net.ru"><font
face="Tahoma" color="white" size="5"><b>НОВИНКИ!
<font face="Tahoma" color="yellow" size="5">_____ Коллекции часов 2OO7 года от</b></font></a></center></td>
</tr>
<tr>
<td bgcolor="#FFCC00"><div align="center"><a href="http://magazinchasoff.net.ru"><font
face="Tahoma" color="RED" size="7"><b>Pateк Philiррe, <font color="black">Rаdо,
<font color="red">Сartiеr, <font color="black">Вreguеt <font color="red">за
$ 228!</b></font></a></div></td>
</tr>
<tr>
<td bgcolor="#006600"><p align="center"><font face="Tahoma" color="white"
size="5"><b>+ ВТ0РЫЕ ЧAСЫ В П0ДАРОК!</font><br>
</p>
<p align="center"><font face="Tahoma" color="yellow" size="3"><b>Более
180 моделей kопий швейцарских часов в наличии. Сборка: Германия<br>
Гарантия: 1 год, 6 месяцев. Бесплатная доставка с оплатой после осмотра</font><br>
</p>
<p align="center"><a href="http://magazinchasoff.net.ru"><font face="Tahoma"
color="white" size="5"><b>Интернет салон TIMEFOR.RU</b></font></a><br>
<font face="Tahoma" color="yellow" size="3"><b>тел. 8 (8OO) 20O0-З50 </font><br>
<font face="Tahoma" color="yellow" size="2"><b>(звонок из любого города России
бесплатный)</font></p></td>
</tr>
<tr>
<td bgcolor="#FFCC00"><div align="center"><font face="Tahoma" color="RED"
size="3"><b>> Торопитесь! Количество подарочных часов ограничено! <</b></font></div></td>
</tr>
</table>
</BODY></HTML>
<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1251">
</head>
<body bgcolor="#FBEFEF" class="Normal" lang=RU>
<table cellspacing="0" cellpadding="0">
<tr>
<td bgcolor="#FF0000"><p align="center"><a href="http://www.swisss.pp.ru/?pid=265"><font
color="#FFFF00" size="7" face="Verdana, Arial, Helvetica, sans-serif"><strong>SALE*
50%<font size="3">*</strong></font></a></p></td>
</tr>
<tr>
<tr>
<td bgcolor="#FFFFCC"><p align="center"><a href="http://www.swisss.pp.ru/?pid=265"><font
color="#FF0000" size="6" face="Verdana, Arial, Helvetica, sans-serif"><strong>Швейцарские
часы<br>Rado, Patek Philippe, Rolex</strong></font></a><br>
<a href="http://www.swisss.pp.ru/?pid=265"><font color="#FF0000" size="5" face="Verdana,
Arial, Helvetica, sans-serif"><b>Производства Бельгии в 100 раз дешевле</b></font></a></p>
</td>
</tr>
<tr>
<td></td>
</tr>
<td align="center" bgcolor="#FFCC00"><font color="#000000" size="2" face="Verdana,
Arial, Helvetica, sans-serif"><b>* скидка 50% на вторые по стоимости часы при заказе
2-х и более моделей</b></font>
<br><font color="#FF0000" size="4" face="Verdana, Arial, Helvetica, sans-serif"><b>При
покупке 1-х часов - Сумка холодильник в подарок!</font></td>
</tr>
<tr>
<td width="733" bgcolor="#FF0000"><p align="center"><font color="#FFFF00"
size="4" face="Verdana, Arial, Helvetica, sans-serif">Каталог и заказ часов: </font><a
href="http://www.swisss.pp.ru/?pid=265"><font color="#FFFF00" size="6" face="Verdana,
Arial, Helvetica, sans-serif"><strong>swisss.pp.ru</strong></font></a>
<br><font color="#FFFFFF" size="3" face="Verdana, Arial, Helvetica, sans-serif"><strong>ICQ:
256-629-734 / Skype: nikolai9708</strong></font></p>
</td>
</tr>
</table>
</body>
</html>
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
While at it, please fold that svn commit list back into commits@httpd. Bill Justin Erenkrantz wrote: > I'd like to propose shutting down test-dev@httpd and move it all back under > dev@httpd. > > The traffic on test-dev@httpd list doesn't justify a separate list, and the > Apache-Test code is now property of the Apache::Perl PMC, so discussions of > that are now elsewhere too. All that's really left is just httpd's test > cases (which really should be done in view of dev@httpd anyway) and flood > (which, like mod_mbox, might get more lovin' if any posts on it moved to > dev@httpd). > > Any objections? If no one screams, I'll do it next week. -- justin > > . >
Justin Erenkrantz wrote: > > Any objections? If no one screams, I'll do it next week. -- justin +1
Justin Erenkrantz wrote: > I'd like to propose shutting down test-dev@httpd and move it all back under > dev@httpd. > > The traffic on test-dev@httpd list doesn't justify a separate list, and the > Apache-Test code is now property of the Apache::Perl PMC, so discussions of > that are now elsewhere too. All that's really left is just httpd's test > cases (which really should be done in view of dev@httpd anyway) and flood > (which, like mod_mbox, might get more lovin' if any posts on it moved to > dev@httpd). > > Any objections? If no one screams, I'll do it next week. +1 it would be nice if rather than alias test-dev@httpd to dev@httpd the message bounced with some kind of informational message about the new breakdown - we still get A-T questions directed toward test-dev@httpd for people who haven't figured out the proper place yet, and I'm just not paying as much attention to dev@httpd as I used to or ought... --Geoff
Sounds good too me. FY, the new perl list test-dev (at) perl (dot) apache (dot) org ------------------------------------------------------------------------ "Love is not the one you can picture yourself marrying, but the one you can't picture the rest of your life without." "It takes a minute to have a crush on someone, an hour to like someone, and a day to love someone, but it takes a lifetime to forget someone..." Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198 Consultant / http://p6m7g8.net/Resume/resume.shtml Senior Software Engineer - TicketMaster - http://ticketmaster.com On Fri, 16 Dec 2005, Justin Erenkrantz wrote: > I'd like to propose shutting down test-dev@httpd and move it all back under > dev@httpd. > > The traffic on test-dev@httpd list doesn't justify a separate list, and the > Apache-Test code is now property of the Apache::Perl PMC, so discussions of > that are now elsewhere too. All that's really left is just httpd's test > cases (which really should be done in view of dev@httpd anyway) and flood > (which, like mod_mbox, might get more lovin' if any posts on it moved to > dev@httpd). > > Any objections? If no one screams, I'll do it next week. -- justin >
I'd like to propose shutting down test-dev@httpd and move it all back under dev@httpd. The traffic on test-dev@httpd list doesn't justify a separate list, and the Apache-Test code is now property of the Apache::Perl PMC, so discussions of that are now elsewhere too. All that's really left is just httpd's test cases (which really should be done in view of dev@httpd anyway) and flood (which, like mod_mbox, might get more lovin' if any posts on it moved to dev@httpd). Any objections? If no one screams, I'll do it next week. -- justin
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
Filin A. wrote: > But after I read your question I made an experiment > whith my system httpd.conf and php.ini and checked > phpinfo() output. > > I've set the extension_dir in php.ini to the wrong > directory and assigned correct value in the > httpd.conf. It's strange but though phpinfo() > acknowledges my httpd.conf extension_dir as a > 'Local Value', extensions are not loaded. That rules out Apache-Test as the root cause of the problem. If I were trying to debug this, I'd very carefully compare the output of phpinfo() in an environment that works with the output of phpinfo() in an environment that doesn't. Hope that helps. Chris -- Chris Shiflett Brain Bulb, The PHP Consultancy http://brainbulb.com/
Hi. Geoff: > hmm, that's a good point. t/conf/extra.conf.in only affects php tests > that > run inside the server, such as t/response/TestAPI/foo.php. Nope. My test is in the t/response/TestPHP/ Chris: > You might try getting rid of the conditional > statement, just to see if > that's the problem. Nope. Removing of the condition doesn't solve the problem :( > By the way, how are you testing to see whether this > works? Is it the > output of phpinfo()? Mm.. actually I just looked into the error_log... But after I read your question I made an experiment whith my system httpd.conf and php.ini and checked phpinfo() output. I've set the extension_dir in php.ini to the wrong directory and assigned correct value in the httpd.conf. It's strange but though phpinfo() acknowledges my httpd.conf extension_dir as a 'Local Value', extensions are not loaded. It looks like settig the extension_dir in a httpd.conf (or in an extra.conf.in) just don't work with my PHP 4.3.4 :( I would appreciate your consideration... -- Filin __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Chris Shiflett wrote: > Hi Filin, > >> I've tride a lot of variants and I even think that >> >> <IfModule @PHP_MODULE@> >> php_admin_value extension_dir /usr/lib/php4/ >> </IfModule> >> >> _should_ work - but it doesn't! I don't know why :( >> (I tried both t/extra.conf.in and >> t/conf/extra.conf.in) > > > The latter is the correct place. > > You might try getting rid of the conditional statement, just to see if > that's the problem. hmm, that's a good point. t/conf/extra.conf.in only affects php tests that run inside the server, such as t/response/TestAPI/foo.php. if you're using t/foo.php-style tests then settings in t/conf/extra.conf.in don't apply. guess we need to figure out how to do that... --Geoff
Hi Filin, > I've tride a lot of variants and I even think that > > <IfModule @PHP_MODULE@> > php_admin_value extension_dir /usr/lib/php4/ > </IfModule> > > _should_ work - but it doesn't! I don't know why :( > (I tried both t/extra.conf.in and > t/conf/extra.conf.in) The latter is the correct place. You might try getting rid of the conditional statement, just to see if that's the problem. By the way, how are you testing to see whether this works? Is it the output of phpinfo()? > Oh. And can you please anyhow lead me at those links? http://shiflett.org/apache-test-demo.tar.gz > Yes, I do like it. Actualy I'm rather fascinated by > the versality and power of your testing suit. Very happy to hear this. :-) Hopefully we can help you get this problem solved. Chris
Hi. Sorry for not writing sooner and thanks for your quick responce. > > 1) Why it is necessary to have a special php.ini for > > testing? > > say you have code that works one system and doesn't work on another. > the problem turns out to be that your php.ini file contains a crucial > difference, but one you didn't think was crucial. I see... > no, anything you need to override you can do locally from > t/extra.conf.in, > such as > > <IfModule @PHP_MODULE> > php_extension_dir /usr/lib/php4/ > </IfModule> > But I can't! I've tride a lot of variants and I even think that <IfModule @PHP_MODULE@> php_admin_value extension_dir /usr/lib/php4/ </IfModule> _should_ work - but it doesn't! I don't know why :( (I tried both t/extra.conf.in and t/conf/extra.conf.in) > chris has links to the sample tarball where you can see tricks like > this in action. Oh. And can you please anyhow lead me at those links? > unfortunately we haven't had the free tuits to document it as well > as we would have liked. but then again, nobody seemed to be using the > php side of things but us. so, welcome - we hope you like it :) Yes, I do like it. Actualy I'm rather fascinated by the versality and power of your testing suit. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
On Wed, Nov 23, 2005 at 03:42:42PM +0100, Oden Eriksson wrote:
> onsdagen den 23 november 2005 15.17 skrev Joe Orton:
> > On Sun, Nov 20, 2005 at 04:43:57PM +0100, Oden Eriksson wrote:
> > > Not so long ago I started packaging apache 2.1.x (rpm) and also run the
> > > perl-framework tests at build time in Mandriva Cooker (development branch
> > > of Mandriva Linux). Ever since I updated openssl-0.9.7i -> openssl-0.9.8a
> > > some ssl tests in the perl-framework stopped working. Is this a known
> > > fact?
> >
> > I see this too now that I have a box running 0.9.8a, all tests which
> > involve a client cert are failing. It looks like a failure on the
> > client side; from a quick manual test mod_ssl seems to be behaving
> > correctly. I'll investigate this further.
> >
> > joe
>
> I forgot to give an update on this. It fixed in Mandriva now. It was because
> openssl must not be built with these (or one of these) "no-mdc2 no-ec no-ecdh
> no-ecdsa".
Thanks. Having spoken to our OpenSSL maintainer it's something more
specifically to do with zlib compression being enabled by default now in
0.9.8a. We're using the below patch for the moment, be careful of the
patent minefield if you start turning on all those cipher suites.
--- openssl-0.9.8a/ssl/ssl_ciph.c.no-builtin-comp 2005-10-01 01:38:20.000000000 +0200
+++ openssl-0.9.8a/ssl/ssl_ciph.c 2005-11-22 16:08:37.000000000 +0100
@@ -203,6 +203,7 @@
static void load_builtin_compressions(void)
{
+#if 0
if (ssl_comp_methods != NULL)
return;
@@ -233,6 +234,7 @@
MemCheck_on();
}
CRYPTO_w_unlock(CRYPTO_LOCK_SSL);
+#endif
}
#endif
onsdagen den 23 november 2005 15.17 skrev Joe Orton: > On Sun, Nov 20, 2005 at 04:43:57PM +0100, Oden Eriksson wrote: > > Not so long ago I started packaging apache 2.1.x (rpm) and also run the > > perl-framework tests at build time in Mandriva Cooker (development branch > > of Mandriva Linux). Ever since I updated openssl-0.9.7i -> openssl-0.9.8a > > some ssl tests in the perl-framework stopped working. Is this a known > > fact? > > I see this too now that I have a box running 0.9.8a, all tests which > involve a client cert are failing. It looks like a failure on the > client side; from a quick manual test mod_ssl seems to be behaving > correctly. I'll investigate this further. > > joe I forgot to give an update on this. It fixed in Mandriva now. It was because openssl must not be built with these (or one of these) "no-mdc2 no-ec no-ecdh no-ecdsa". Tests in neon also failed: 25. cache_verify.......... server child failed: SSL_read failed (-1): decryption failed or bad record mac FAIL (error from server process) 44. session_cache......... server child failed: SSL_accept failed: sslv3 alert bad record mac FAIL (line 849: HTTP error: SSL negotiation failed: SSL error: decryption failed or bad record mac) 48. auth_tunnel_creds..... server child failed: SSL_read failed (-1): decryption failed or bad record mac FAIL (error from server process) cyrus-imap also had problems: http://qa.mandriva.com/show_bug.cgi?id=19882 The tests using this combination passes now: perl-framework (latest from svn) + apache 2.1.9/2.1.10 + openssl-0.9.8a ftp://ftp.sunet.se/pub/Linux/distributions/Mandriva/devel/cooker/SRPMS/contrib/apache2-2.1.9-0.beta.3mdk.src.rpm (it runs tests for php4 and php5 too, not mod_perl yet) > > These are the tests that fails: > > > > t/ssl/basicauth.t 3 2 66.67% 2-3 > > t/ssl/env.t 28 14 50.00% 15-28 > > t/ssl/extlookup.t 2 2 100.00% 1-2 > > t/ssl/fakeauth.t 3 2 66.67% 2-3 > > t/ssl/proxy.t 172 10 5.81% 3-7 116-120 > > t/ssl/require.t 5 2 40.00% 2 5 > > t/ssl/varlookup.t 72 72 100.00% 1-72 > > t/ssl/verify.t 3 1 33.33% 2 > > 13 tests and 1 subtest skipped. > > Failed 8/126 test scripts, 93.65% okay. 105/2919 subtests failed, 96.40% > > okay. > > > > > > Cheers. > > -- > > Regards // Oden Eriksson > > Mandriva: http://www.mandriva.com > > NUX: http://li.nux.se -- Regards // Oden Eriksson Mandriva: http://www.mandriva.com NUX: http://li.nux.se
On Sun, Nov 20, 2005 at 04:43:57PM +0100, Oden Eriksson wrote: > Not so long ago I started packaging apache 2.1.x (rpm) and also run the > perl-framework tests at build time in Mandriva Cooker (development branch of > Mandriva Linux). Ever since I updated openssl-0.9.7i -> openssl-0.9.8a some > ssl tests in the perl-framework stopped working. Is this a known fact? I see this too now that I have a box running 0.9.8a, all tests which involve a client cert are failing. It looks like a failure on the client side; from a quick manual test mod_ssl seems to be behaving correctly. I'll investigate this further. joe > > These are the tests that fails: > > t/ssl/basicauth.t 3 2 66.67% 2-3 > t/ssl/env.t 28 14 50.00% 15-28 > t/ssl/extlookup.t 2 2 100.00% 1-2 > t/ssl/fakeauth.t 3 2 66.67% 2-3 > t/ssl/proxy.t 172 10 5.81% 3-7 116-120 > t/ssl/require.t 5 2 40.00% 2 5 > t/ssl/varlookup.t 72 72 100.00% 1-72 > t/ssl/verify.t 3 1 33.33% 2 > 13 tests and 1 subtest skipped. > Failed 8/126 test scripts, 93.65% okay. 105/2919 subtests failed, 96.40% okay. > > > Cheers. > -- > Regards // Oden Eriksson > Mandriva: http://www.mandriva.com > NUX: http://li.nux.se
Attaching the .t file after compressing. --- "William A. Rowe, Jr." <wrowe@rowe-clan.net> wrote: > And that answers that <grrr> > > Zubin, would you .gz compress your .t file to see if > it comes through? > > __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
Hello. Not so long ago I started packaging apache 2.1.x (rpm) and also run the perl-framework tests at build time in Mandriva Cooker (development branch of Mandriva Linux). Ever since I updated openssl-0.9.7i -> openssl-0.9.8a some ssl tests in the perl-framework stopped working. Is this a known fact? These are the tests that fails: t/ssl/basicauth.t 3 2 66.67% 2-3 t/ssl/env.t 28 14 50.00% 15-28 t/ssl/extlookup.t 2 2 100.00% 1-2 t/ssl/fakeauth.t 3 2 66.67% 2-3 t/ssl/proxy.t 172 10 5.81% 3-7 116-120 t/ssl/require.t 5 2 40.00% 2 5 t/ssl/varlookup.t 72 72 100.00% 1-72 t/ssl/verify.t 3 1 33.33% 2 13 tests and 1 subtest skipped. Failed 8/126 test scripts, 93.65% okay. 105/2919 subtests failed, 96.40% okay. Cheers. -- Regards // Oden Eriksson Mandriva: http://www.mandriva.com NUX: http://li.nux.se
cc'ing chris :) > I think a line in the t/conf/php.ini: > > extension_dir = "./" > > means that php seeks libraries in the current > directory, while those > libraries are in the /usr/lib/php4/. hmm, could be. chris would know better. > Thereby I have 2 > questions: > 1) Why it is necessary to have a special php.ini for > testing? for the same reason that Apache-Test maintains all its own configuration files, really - consistency, principle of least surprise, and so on. think of it like this... say you have code that works one system and doesn't work on another. the problem turns out to be that your php.ini file contains a crucial difference, but one you didn't think was crucial. if your tests relied on the installed php.ini file then you'd have the exact same problem on each box when running the tests, on one box it would fail and on one box it would pass. this is Very Bad from a testing point of view - tests should create a very specific environment in which to exercise your code, one where all the variables are known. using our own php.ini file (and own httpd.conf, etc) means that the described circumstance would never happen - the tests would pass on both systems letting you know immediately that your production environment is _not_ the same as your testing environment. and that is Good from a testing point of view. > 2) How can I test (in a sane manner) php code with > functions from > dynamic libraries? I don't know the specifics, but to alter any php.ini setting you would create t/conf/extra.conf.in and use a php variable to override the default settings in php.ini > > I've tried to copy mysql.so in the "current > directory", in all > meanings of "current" which I could imagine but > without any success. > I've successfully tried to modify the > Apache::TestConfigPHP > so that it generates now > 'extension_dir="/usr/lib/php4/"', > but I don't think it is a good solving... no, anything you need to override you can do locally from t/extra.conf.in, such as <IfModule @PHP_MODULE> php_extension_dir /usr/lib/php4/ </IfModule> or somesuch - I'm not really a php guy :) chris has links to the sample tarball where you can see tricks like this in action. unfortunately we haven't had the free tuits to document it as well as we would have liked. but then again, nobody seemed to be using the php side of things but us. so, welcome - we hope you like it :) --Geoff
Hi all. I'm trying to use Apache::Test module for testing my php driven site (Linux, Apache 2.0, PHP 4.3). Everything works pretty good, but when I try to test a php page which uses any of mysql functions - the test fails and the error_log contains these lines: ... PHP Warning: Unknown(): Unable to load dynamic library './mysql.so' - ./mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0 PHP Warning: Unknown(): Unable to load dynamic library './xmlrpc.so' - ./xmlrpc.so: cannot open shared object file: No such file or directory in Unknown on line 0 ... [Client 127.0.0.1] PHP Fatal error: Call to undefined function: mysql_connect() in /home/filin/work-varavka/staff/htdocs/_inc/dbconnect.inc.php on line 8 ... I think a line in the t/conf/php.ini: extension_dir = "./" means that php seeks libraries in the current directory, while those libraries are in the /usr/lib/php4/. Thereby I have 2 questions: 1) Why it is necessary to have a special php.ini for testing? 2) How can I test (in a sane manner) php code with functions from dynamic libraries? I've tried to copy mysql.so in the "current directory", in all meanings of "current" which I could imagine but without any success. I've successfully tried to modify the Apache::TestConfigPHP so that it generates now 'extension_dir="/usr/lib/php4/"', but I don't think it is a good solving... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
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.,
t/modules/access.t) to *not* do that; instead, have
Makefile.PL prepare appropriate subdirectory configs
for them. Why? So t/TEST can be used to test a
remote server.
* problems with -d perl mode, doesn't work as documented
Message-ID: <3BD10479.2020506@stason.org>
Date: Sat, 20 Oct 2001 12:58:33 +0800
Subject: Re: perldb
Tests to be written:
* t/apache
- simulations of network failures (incomplete POST bodies,
chunked and unchunked; missing POST bodies; slooow
client connexions, such as taking 1 minute to send
1KiB; ...)
* t/modules/autoindex
- something seems possibly broken with inheritance on 2.0
* t/ssl
- SSLPassPhraseDialog exec:
- SSLRandomSeed exec:
flood STATUS: -*-text-*-
Last modified at [$Date: 2004-11-24 19:36:41 -0500 (Wed, 24 Nov 2004) $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2001
milestone-01: Tagged July 11, 2001 (tag lost during transfer)
RELEASE SHOWSTOPPERS:
* "Everything needs to work perfectly"
Other bugs that need fixing:
* I get a SIGBUS on Darwin with our examples/round-robin-ssl.xml
config, on the second URL. I'm using OpenSSL 0.9.6c 21 dec 2001.
* iPlanet sends "Content-length" - there is a hack in there now
to recognize it. However, all HTTP headers need to be normalized
before checking their values. This isn't easy to do. Grr.
* OpenSSL 0.9.6
Segfaults under high load. Upgrade to OpenSSL 0.9.6b.
Aaron says: I just found a big bug that might have been causing
this all along (we weren't closing ssl sockets).
How can I reproduce the problem you were seeing
to verify if this was the fix?
* SEGVs when /tmp/.rnd doesn't exist are bad. Make it configurable
and at least bomb with a good error message. (See Doug's patch.)
Status: This is fixed, no?
* If APR has disabled threads, flood should as well. We might want
to have an enable/disable parameter that does this also, providing
an error if threads are desired but not available.
* flood needs to clear pools more often. With a long running test
it can chew up memory very quickly. We should just bite the bullet
and create/destroy/clear pools for each level of our model:
farm, farmer, profile, url/request-cycle, etc.
* APR needs to have a unified interface for ephemeral port
exhaustion, but aparently Solaris and Linux return different
errors at the moment. Fix this in APR then take advantage of
it in flood.
* The examples/analyze-relative scripts fail when there are less
than 5 unique URLs.
Other features that need writing:
* More analysis and graphing scripts are needed
* Write robust tool (using tethereal perhaps) to take network dumps
and convert them to flood's XML format.
Status: Justin volunteers. Aaron had a script somewhere that is
a start. Jacek is working on a Mozilla application, codename
"Flood URL bag" (much like Live HTTP Headers) and small
HTTP proxy.
* Get chunked encoding support working.
Status: Justin volunteers. He got sidetracked by the httpd
implementation of input filtering and never finished
this. This is a stopgap until apr-serf is completed.
* Maybe we should make randfile and capath runtime directives that
come out of the XML, instead of autoconf parameters.
* We are using apr_os_thread_current() and getpid() in some places
when what we really want is a GUID. The GUID will be used to
correlate raw output data with each farmer. We may wish to print
a unique ID for each of farm, farmer, profile, and url to help in
postprocessing.
* We are using strtol() in some places and strtoll() in others.
Pick one (Aaron says strtol(), but he's not sure).
* Validation of responses (known C-L, specific strings in response)
Status: Justin volunteers
* HTTP error codes (ie. teach it about 302s)
Justin says: Yeah, this won't be with round_robin as implemented.
Need a linked list-based profile where we can insert
new URLs into the sequence.
* Farmer (Single-thread, multiple profiles)
Status: Aaron says: If you have threads, then any Farmer can be
run as part of any Farm. If you don't have threads, you can
currently only run one Farmer named "Joe" right now (this will
be changed so that if you don't have threads, flood will attempt
to run all Farmers in serial under one process).
* Collective (Single-host, multiple farms)
This is a number of Farms that have been fork()ed into child processes.
* Megaconglomerate (Multiple hosts each running a collective)
This is a number of Collectives running on a number of hosts, invoked
via RSH/SSH or maybe even some proprietary mechanism.
* Other types of urllists
a) Random / Random-weighted
b) Sequenced (useful with cookie propogation)
c) Round-robin
d) Chaining of the above strategies
Status: Round-robin is complete.
* Other types of reports
Status: Aaron says: "simple" reports are functional. Justin added
a new type that simply prints the approx. timestamp when
the test was run, and the result as OK/FAIL; it is called
"easy reports" (see flood_easy_reports.h).
Furthermore, simple_reports and easy_reports both print
out the current requesting URI line.
Documentation that needs writing:
* Documentation? What documentation? RTFS?
Status: Justin volunteers. He'll probably use Anakia for user
docs and doxygen for source code comments.
* Feature set
We'll have to eventually write down all the features we support,
which will most likely come out to be the various XML parameters
we support.
Available Patches:
Open issues:
* Ponder using apr-serf in flood
Status: This requires apr-serf to be written. Chicken and egg.
Ideally, apr-serf would handle buckets, filters, and
other cool stuff. However, this isn't the highest of
priorities.
* Validating XML Parser?
Justin says: I don't think we want this. We want a standalone
validator.
Aaron says: I strongly feel we should have this turned on at
least for the invoking "Megaconglomerate". The added
overhead for validating when we're already parsing
will be minimal. It will not affect the results of
the tests. It only happens when a new flood process
is created (directly or via rsh/ssh), not when invoking
a collective, farm, farmer, or profile. What it gives
us from the user's standpoint is far greater than
the impact of the added startup overhead.
(Maybe a flood argument that disables it for when
some UI wrapper already did the checking or if it's
being invoked as part of a megaconglomerate (rsh/ssh).)
* Supporting use of installed APR / APR-util
Justin says: Requires changes to APR/APR-util to make it install
the right stuff. We currently rely on the source.
* Mandrake Linux 8.0 and OpenSSL 0.9.6a just aren't coexisting at all.
The problem seems to be that OpenSSL is refusing to initialize the
PRNG. Go figure. I give up on this for now, but it is a big nasty
bug in something somewhere. This code works on Solaris/Intel.
That's all I'll say on the matter for now.
* Report Aggregation
We're not sure how to handle reporting quite yet. We'd like to keep
it open ended and flexible, but that will be difficult to do while
maintaining the ability to run a huge variety of tests.
* WebLogic 5.10 Service Pack 9
No one told BEA how to make an HTTP server. Send it Connection: Close
and a cookie, and it'll respond with Connection: Keep-Alive (no cookie
and it honors Connection: Close). That's wrong.
And that answers that <grrr> Zubin, would you .gz compress your .t file to see if it comes through?
Since Zubin's posts for the .t file kept failing (yet I can see them in my own email client from Zubin) - I thought I'd try resending for him the new pr37145.t - and see if Thunderbird + apmail does any better. Zubin Kika wrote: > Don't know why the other file didn't make it. > Attaching pr37145.t again. > > Zubin > > --- Zubin Kika <zubin_qc@yahoo.com> wrote: > > >>Hi, >> >>Thank you Joe for your suggestions. >>I have incorporated the changes and attached two >>files: >> 1)pr37145.t: This file is to be placed in >>t/ssl/ >> 2)testrev_proxy.pl: This file is to be >>placed >>in t/htdocs/modules/cgi/ >> >>Please review. >> >>With regards, >>Zubin >> >>--- Joe Orton <jorton@redhat.com> wrote: >> >> >>>On Wed, Oct 26, 2005 at 01:30:22AM -0700, Zubin >> >>Kika >> >>>wrote: >>> >>>>The patch is attached. >>>>It contains the following files: >>>>t/ssl/proxy_bug37145.t :The script file >>>>t/htdocs/test.txt :Test file of size 100Kb >>>>t/htdocs/test1.txt :Test file of size less than >> >>8 >> >>>Kb >>> >>>>t/htdocs/test2.txt :Test file of size 8Kb >>>>t/htdocs/modules/cgi/testrev_proxy.pl :Perl file >>> >>>that >>> >>>>will handle the posted data >>>> >>>>Request you to please review the same. >>> >>>Thanks for the contribution. >>> >>>- the CGI script should not rely on CGI.pm >>>- call the new test simply "t/ssl/pr37145.t" >>>- attach files not tarballs when posting new code >>>- create a new directory for new htdocs >>>(t/htdocs/modules/ssl) >>>- a CGI script which outputs 100Kb of data would >> >>be >> >>>preferable to >>>adding a 100Kb file directly to the repos >>>- follow the normal code style (indenting, >>>whitespace etc) for the .t >>>code; should be something like: >>> >> > http://perl.apache.org/docs/2.0/devel/core/coding_style.html#Coding_Style_Guide > >>> >>>joe >>> >> >> >> >> >>__________________________________ >>Yahoo! Mail - PC Magazine Editors' Choice 2005 >>http://mail.yahoo.com > > > > > __________________________________ > Yahoo! FareChase: Search multiple travel sites in one click. > http://farechase.yahoo.com
On the mod_python side we got a 3.2.2 beta out and will try to get 3.2.? final done before Apachecon (hopefully). The last release (not counting security fix ones) was 20 months ago, so this is pretty significant. Grisha On Mon, 14 Nov 2005, Roy T. Fielding wrote: > Much to my surprise, I apparently have a board report due yesterday > for this Wednesday's board meeting. Do we have any ASF issues that > need reporting to the board, aside from what is in STATUS*? > Any choice commentary? Does anyone else feel like we have too many > dev lists for one project? > > ....Roy >
"Roy T. Fielding" <fielding@gbiv.com> writes: > Do we have any ASF issues that need reporting to the board, Nothing new to report wrt apreq. -- Joe Schaefer
Roy T.Fielding wrote: > Much to my surprise, I apparently have a board report due yesterday > for this Wednesday's board meeting. Do we have any ASF issues that > need reporting to the board, aside from what is in STATUS*? > Any choice commentary? Does anyone else feel like we have too many > dev lists for one project? httpd prepares to release 2.2, many developers are itching for a pre-ApacheCon candidate, with a formal release announcement at the Opening Plenary of the con. At least, that's the desire that a few of the primary contributors have expressed, as the Hackathon is a golden opportunity to dot the i's and cross the t's. Showstoppers continue to shrink. httpd-docs continues to attract new translators, and new languages. Much work is afoot to prepare for httpd 2.2. cli-dev subproject has little to report, except that user-to-user peer support is working well on cli-users, and the next potential snapshot is awaiting some commentary and feedback from the dev list. With a few more nags, we anticipate a new mod_aspdotnet release for .NET 1.0/1.1 within the next month, and with the release of the '1 year free' Microsoft Visual C++, hope to have a .NET 2.0 flavor of the module in development around that timeframe that most anyone can build from source. Bill
Much to my surprise, I apparently have a board report due yesterday for this Wednesday's board meeting. Do we have any ASF issues that need reporting to the board, aside from what is in STATUS*? Any choice commentary? Does anyone else feel like we have too many dev lists for one project? ....Roy
Don't know why the other file didn't make it. Attaching pr37145.t again. Zubin --- Zubin Kika <zubin_qc@yahoo.com> wrote: > Hi, > > Thank you Joe for your suggestions. > I have incorporated the changes and attached two > files: > 1)pr37145.t: This file is to be placed in > t/ssl/ > 2)testrev_proxy.pl: This file is to be > placed > in t/htdocs/modules/cgi/ > > Please review. > > With regards, > Zubin > > --- Joe Orton <jorton@redhat.com> wrote: > > > On Wed, Oct 26, 2005 at 01:30:22AM -0700, Zubin > Kika > > wrote: > > > The patch is attached. > > > It contains the following files: > > > t/ssl/proxy_bug37145.t :The script file > > > t/htdocs/test.txt :Test file of size 100Kb > > > t/htdocs/test1.txt :Test file of size less than > 8 > > Kb > > > t/htdocs/test2.txt :Test file of size 8Kb > > > t/htdocs/modules/cgi/testrev_proxy.pl :Perl file > > that > > > will handle the posted data > > > > > > Request you to please review the same. > > > > Thanks for the contribution. > > > > - the CGI script should not rely on CGI.pm > > - call the new test simply "t/ssl/pr37145.t" > > - attach files not tarballs when posting new code > > - create a new directory for new htdocs > > (t/htdocs/modules/ssl) > > - a CGI script which outputs 100Kb of data would > be > > preferable to > > adding a 100Kb file directly to the repos > > - follow the normal code style (indenting, > > whitespace etc) for the .t > > code; should be something like: > > > http://perl.apache.org/docs/2.0/devel/core/coding_style.html#Coding_Style_Guide > > > > joe > > > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
Hi,
Thank you Joe for your suggestions.
I have incorporated the changes and attached two
files:
1)pr37145.t: This file is to be placed in
t/ssl/
2)testrev_proxy.pl: This file is to be placed
in t/htdocs/modules/cgi/
Please review.
With regards,
Zubin
--- Joe Orton <jorton@redhat.com> wrote:
> On Wed, Oct 26, 2005 at 01:30:22AM -0700, Zubin Kika
> wrote:
> > The patch is attached.
> > It contains the following files:
> > t/ssl/proxy_bug37145.t :The script file
> > t/htdocs/test.txt :Test file of size 100Kb
> > t/htdocs/test1.txt :Test file of size less than 8
> Kb
> > t/htdocs/test2.txt :Test file of size 8Kb
> > t/htdocs/modules/cgi/testrev_proxy.pl :Perl file
> that
> > will handle the posted data
> >
> > Request you to please review the same.
>
> Thanks for the contribution.
>
> - the CGI script should not rely on CGI.pm
> - call the new test simply "t/ssl/pr37145.t"
> - attach files not tarballs when posting new code
> - create a new directory for new htdocs
> (t/htdocs/modules/ssl)
> - a CGI script which outputs 100Kb of data would be
> preferable to
> adding a 100Kb file directly to the repos
> - follow the normal code style (indenting,
> whitespace etc) for the .t
> code; should be something like:
>
http://perl.apache.org/docs/2.0/devel/core/coding_style.html#Coding_Style_Guide
>
> joe
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com