Hi,
this is quite an old thread. But now I have found why it was not working.
On Sunday 19 December 2004 23:34, Stas Bekman wrote:
> Torsten Foertsch wrote:
> > On Thursday 16 December 2004 17:28, Stas Bekman wrote:
[...]
> right, but the idea was to grep and jump to the code following it, which
Torsten Foertsch wrote:
On Thursday 16 December 2004 17:28, Stas Bekman wrote:
grep the source for reconfigure() which I think will enforce the re-cache.
Sorry, I could not find it. Simply changing refresh to reconfigure yields:
Sorry, I should have said just 'reconfigure', which is not a method.
On Thursday 16 December 2004 17:28, Stas Bekman wrote:
> grep the source for reconfigure() which I think will enforce the re-cache.
Sorry, I could not find it. Simply changing refresh to reconfigure yields:
Can't locate object method "reconfigure" via package "Apache::TestRunPerl" at
/home/r2/wo
Geoffrey Young wrote:
right, but you can't really run SSL tests with a manually coded client,
^
can you?
yes, you can. see the "Live" tests in Apache-SSLLookup.
I'm not sure what do you mean, I've looked at
http://search.cp
>>> right, but you can't really run SSL tests with a manually coded client,
^
>>> can you?
>>
>>
>>
>> yes, you can. see the "Live" tests in Apache-SSLLookup.
>
>
> I'm not sure what do you mean, I've looked at
> http://se
Geoffrey Young wrote:
I suppose this would not work for the automatically built response tests
which use the default port.
right, but you can't really run SSL tests with a manually coded client,
can you?
yes, you can. see the "Live" tests in Apache-SSLLookup.
I'm not sure what do you mean, I've
William McKee wrote:
> On Thu, Dec 16, 2004 at 11:28:42AM -0500, Stas Bekman wrote:
>
>>Right, because as you've figured out t/conf/apache_test_config.pm is a
>>cached version of the the test setup data. So you need to do a cleanup
>>before reconfiguring things so that file gets updated. Note
Stas Bekman wrote:
> William McKee wrote:
> [...]
>
>> When I want to use the SSL connection in a request test, I
>> do the following:
>>
>> my $config = Apache::Test::config();
>> Apache::TestRequest::module('ssl');
>> my $hostport = Apache::TestRequest::hostport();
>
>
> BTW, A-T 1.17
William McKee wrote:
[...]
When I want to use the SSL connection in a request test, I
do the following:
my $config = Apache::Test::config();
Apache::TestRequest::module('ssl');
my $hostport = Apache::TestRequest::hostport();
BTW, A-T 1.17 has a new shortcut which does all the above:
$url =
On Thu, Dec 16, 2004 at 11:28:42AM -0500, Stas Bekman wrote:
> Right, because as you've figured out t/conf/apache_test_config.pm is a
> cached version of the the test setup data. So you need to do a cleanup
> before reconfiguring things so that file gets updated. Note that you
> perform things A
Torsten Foertsch wrote:
On Wednesday 15 December 2004 20:46, Stas Bekman wrote:
Torsten Foertsch wrote:
But how do I know it in the tests? Is there another way except of
scanning conf/httpd.conf?
You do:
use Apache::Test;
plan tests => 5, need_module 'ssl';
It's documented in the Apache::Test manpa
On Wednesday 15 December 2004 20:46, Stas Bekman wrote:
> Torsten Foertsch wrote:
> > But how do I know it in the tests? Is there another way except of
> > scanning conf/httpd.conf?
>
> You do:
>
> use Apache::Test;
> plan tests => 5, need_module 'ssl';
>
> It's documented in the Apache::Test manpa
Torsten Foertsch wrote:
Hi,
I want my test suite run once with mod_ssl.so loaded and once without. My
TEST.PL looks this:
use strict;
use warnings FATAL => 'all';
use lib qw(lib);
use Apache::TestRunPerl ();
my $I=Apache::TestRunPerl->new;
$I->run(@ARGV);
Apache::TestConfig::autoconfig_skip_modul
Hi,
I want my test suite run once with mod_ssl.so loaded and once without. My
TEST.PL looks this:
use strict;
use warnings FATAL => 'all';
use lib qw(lib);
use Apache::TestRunPerl ();
my $I=Apache::TestRunPerl->new;
$I->run(@ARGV);
Apache::TestConfig::autoconfig_skip_module_add('mod_ssl.c')
14 matches
Mail list logo
