[users@httpd] Searching for Apache Test Framework or Test Harness

[Andrew Joshwa]

Hi,

Is there any Open Source Apache Test Framework or Test Harness available
for Apache 2.4?

Basically I want  to run the complete test for my Apache installation.

For e.g. The test framework should be able to test all the Modules
available with Apache 2.4

Regards,
Andrew

Re: [users@httpd] Searching for Apache Test Framework or Test Harness

[Stefan Eissing]

Hi Andrew,

the overall test suite is at 
.

For some modules, additional test suites are available. For example the ones in 
 and .

Cheers, Stefan

> Am 04.06.2019 um 11:23 schrieb Andrew Joshwa <4andrewjosh...@gmail.com>:
> 
> Hi,
> 
> Is there any Open Source Apache Test Framework or Test Harness available for 
> Apache 2.4?
> 
> Basically I want  to run the complete test for my Apache installation.
> 
> For e.g. The test framework should be able to test all the Modules available 
> with Apache 2.4
> 
> Regards,
> Andrew


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Can't connect to server on 443 ... no log information being generated

[William A Rowe Jr]

On Mon, Jun 3, 2019 at 11:08 PM Geoff Russell 
wrote:

> Hi Douglas,
>
> Thanks for your help.   I've spent about 6 hours on this problem and it
> has just vanished ...
>
> I tried elinks as a substitute for telnet ... telnet does succeed in the
> socket handshake, to is useful for quick test of that part of the
> connection.
>

Just for future reference, openssl s_client is the usual way to test the
connection stack to the server, which gives you the options to force
specific versions of tls, specific ciphers, etc.

Re: [users@httpd] Can't connect to server on 443 ... no log information being generated

[Geoff Russell]

On Wed, Jun 5, 2019 at 9:36 AM William A Rowe Jr 
wrote:

> On Mon, Jun 3, 2019 at 11:08 PM Geoff Russell 
> wrote:
>
>> Hi Douglas,
>>
>> Thanks for your help.   I've spent about 6 hours on this problem and it
>> has just vanished ...
>>
>> I tried elinks as a substitute for telnet ... telnet does succeed in the
>> socket handshake, to is useful for quick test of that part of the
>> connection.
>>
>
> Just for future reference, openssl s_client is the usual way to test the
> connection stack to the server, which gives you the options to force
> specific versions of tls, specific ciphers, etc.
>

Thanks for the tip. After about 6 hours of investigation ... the problem
has vanished as mysteriously as it arrived. I cleaned up some irrelevant
router port forwarding entries and everything started working.

Cheers,
Geoff