I finally figured out that this works:
$Apache::TestRequest::RedirectOK = 0;
Again, more docs would be welcome.
well, it's not more docs, but whenever I'm in search of some bit of
functionality I check the tests in the perl-framework/t/modules directory,
which you'll find if you checkout the
Geoffrey Young wrote:
1. The documentation is pretty lacking.
As Geoff pointed out, this statement is incorrect. The document:
http://perl.apache.org/docs/general/testing/testing.html
should answer most of your questions.
2. The tests are being run from t/, rather then from the root of the
On Tue, 17 Jun 2003, Stas Bekman wrote:
[ .. ]
David, please test this patch. This version performs the
cleanup only during 'make install'. what I'm not sure about is
whether it handles correctly some weird paths when creating the
packlist. I think it should work, since nothing is passed via
I've uploaded 1.03's release candidate. If nobody finds any faults, I'll
upload it tomorrow on CPAN. (libapreq needs to rely on 1.03 fixes to release
its 1.2's version).
Please try it out:
http://www.apache.org/~stas/Apache-Test-1.03-dev.tar.gz
Test it with mod_perl 1.0:
perl Makefile.PL -httpd
Stas Bekman wrote:
I've uploaded 1.03's release candidate. If nobody finds any faults,
I'll upload it tomorrow on CPAN. (libapreq needs to rely on 1.03 fixes
to release its 1.2's version).
Please try it out:
http://www.apache.org/~stas/Apache-Test-1.03-dev.tar.gz
Tests OK for me - Windows XP /
Hi,
5.0-RELEASE FreeBSD, apache 1.3.27, mod_perl 1.27, perl 5.8.0
All tests successful.
-Original Message-
From: Stas Bekman [EMAIL PROTECTED]
To: modperl@perl.apache.org,httpd-test-dev list [EMAIL PROTECTED]
Date: Wed, 18 Jun 2003 19:13:46 +1000
Subject: [RELEASE CANDIDATE]
Now just awaiting a confirmation from David and I'll put Apache::Test
1.03 on CPAN.
David, if you see this before tomorrow, simpy try the latest cvs, I have
already committed the needed change. Hopefully it does do the right thing for you.
On Wednesday, June 18, 2003, at 05:13 AM, Stas Bekman wrote:
I've uploaded 1.03's release candidate. If nobody finds any faults,
I'll upload it tomorrow on CPAN. (libapreq needs to rely on 1.03 fixes
to release its 1.2's version).
Please try it out:
On Tuesday, June 17, 2003, at 08:02 PM, Stas Bekman wrote:
Geoffrey Young wrote:
1. The documentation is pretty lacking.
As Geoff pointed out, this statement is incorrect. The document:
http://perl.apache.org/docs/general/testing/testing.html
should answer most of your questions.
It's incorrect
On Tuesday, June 17, 2003, at 08:04 PM, Stas Bekman wrote:
I finally figured out that this works:
$Apache::TestRequest::RedirectOK = 0;
Again, more docs would be welcome.
Patches are welcome.
Glad to hear it! Look for one shortly.
David
--
David Wheeler AIM:
On Wednesday, June 18, 2003, at 07:30 AM, Stas Bekman wrote:
Now just awaiting a confirmation from David and I'll put Apache::Test
1.03 on CPAN.
David, if you see this before tomorrow, simpy try the latest cvs, I
have already committed the needed change. Hopefully it does do the
right thing
On Tuesday, June 17, 2003, at 07:22 PM, Geoffrey Young wrote:
I finally figured out that this works:
$Apache::TestRequest::RedirectOK = 0;
Again, more docs would be welcome.
well, it's not more docs, but whenever I'm in search of some bit of
functionality I check the tests in the
--On Tuesday, June 17, 2003 4:34 PM -0400 Geoff Thorpe [EMAIL PROTECTED]
wrote:
Well first off, the original backtrace showed a segfault down inside the
bowels of the error handlers, something to do with CRYPTO_thread_id()
IIRC. That you were getting this, combined with the fact you couldn't get
--On Tuesday, June 17, 2003 7:49 PM -0700 Greg Stein [EMAIL PROTECTED] wrote:
Hmm. It seems possible that deliver_report could fail before generating any
response. Thus, we want to test what the situation is, and deliver the error
or perform the new ah, crap. punt option.
The logic would be like
On Tue, Jun 17, 2003 at 11:33:48PM -0700, Justin Erenkrantz wrote:
--On Tuesday, June 17, 2003 7:49 PM -0700 Greg Stein [EMAIL PROTECTED]
wrote:
Hmm. It seems possible that deliver_report could fail before generating any
response. Thus, we want to test what the situation is, and deliver the
--On Tuesday, June 17, 2003 11:49 PM -0700 Greg Stein [EMAIL PROTECTED] wrote:
Definitely possible. But we have no better measure to detect that some
output has been generated. Once *some* output has been started (and, say, it
has been buffered by some filter), then the only likely error that
Does the Apache 1.x method ap_get_module_config exist for Apache 2 also. If no what
is the counterpart for this on Apache 2.x
Where can I find the info. on various Apache 1.x routines counterpart for Apache 2.x.
Thanks,
Rahul Kohli
Hi there,
On June 16, 2003 10:14 pm, William A. Rowe, Jr. wrote:
At 08:13 PM 6/16/2003, Justin Erenkrantz wrote:
The change to move OpenSSL's initialization to ssl_hook_pre_config is
busted when mod_ssl is a DSO. It will try to call all of the OpenSSL
init sequences twice which I don't
Hi,
5.0-RELEASE FreeBSD, apache 1.3.27, mod_perl 1.27, perl 5.8.0
All tests successful.
-Original Message-
From: Stas Bekman [EMAIL PROTECTED]
To: [EMAIL PROTECTED],httpd-test-dev list [EMAIL PROTECTED]
Date: Wed, 18 Jun 2003 19:13:46 +1000
Subject: [RELEASE CANDIDATE] Apache::Test
Rahul Kohli wrote:
Does the Apache 1.x method ap_get_module_config exist for Apache 2 also.
grep for it in Apache's include directory... (you'll find it)
Where can I find the info. on various Apache 1.x routines counterpart for Apache 2.x.
fairly simple renames of 1.3 functions show up in
Title: [PATCH] EventLog display name patch
The current nt_eventlog implementation has the hardcoded Apache Service as the event log application name. This can be problematic if you have multiple instances of Apache running on the same box.
If, for instance, you register multiple apache
Title: [PATCH] EventLog display name patch
BTW, the service.c
patch should also take care of the following bug. If your configuration file
has a syntax error, you will get something like this in your event log:
The
Apache service named reported the
following error:
Syntax error on
-Original Message-
From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]
[SNIP]
On this same tangent, do we need to be doing all of the CRYPTO_lock
stuff?
I don't believe we are doing that. And, I know in flood, we had lots of
problems until we called them. So, I think mod_ssl should be
Hi,
On June 18, 2003 02:28 am, Justin Erenkrantz wrote:
Finally got a chance to dig some more and found that if I add:
CRYPTO_set_id_callback(openssl_id);
to ssl_hook_pre_config before the ENGINE_load_builtin_engines and where
openssl_id is defined as:
static unsigned long
At 09:59 AM 6/18/2003, Juan Rivera wrote:
The current nt_eventlog implementation has the hardcoded Apache Service as the
event log application name. This can be problematic if you have multiple instances of
Apache running on the same box.
To fix this, I made midifications on two files:
The
[Reposting patch, with gstein's added check for r-sent_bodyct.]
Have mod_dav deal with errors that happen during a streamy provider response.
* mod_dav.c (dav_method_propfind, dav_method_report): if the dav
provider throws an error in the middle of streaming a response, have
mod_dav log an
Title: RE: [PATCH] EventLog display name patch
Is there any other way to get the display name? I look for other ways but couldn't figure out another approach.
Juan
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 18, 2003 3:43 PM
To:
At 03:04 PM 6/18/2003, Juan Rivera wrote:
Is there any other way to get the display name? I look for other ways but couldn't
figure out another approach.
From the registry. It just looks like we look up the display name a little
too late for some classes of errors.
Working on this.
Bill
Hi all,
I'm currently writing an Apache module (Apache 1.3.27) for virtual
masshosting based on a SQL backend (currently MySQL later on
PostgreSQL). Therefore I'm searching for information about the
differences between requests (request_rec) and servers (server_rec).
Can anybody tell me the
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2003/06/02 13:13:45 $]
Release:
1.3.28-dev: In development. Jim proposes a release mid-June
and offers to be RM.
1.3.27: Tagged September 30, 2002. Announced Oct 3, 2002.
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2003/06/17 15:20:02 $]
Release:
2.0.47 : in development
2.0.46 : released May 28, 2003 as GA.
2.0.45 : released April 1, 2003 as GA.
2.0.44 : released January 20, 2003 as GA.
APACHE 2.1 STATUS: -*-text-*-
Last modified at [$Date: 2003/05/29 15:07:11 $]
Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
2.1.0 : in development
Please consult the following STATUS files for information
on related
32 matches
Mail list logo
