Re: http2 tests

[Kaspar Brand]

On 14.10.2015 14:55, Eric Covener wrote:
> On Wed, Oct 14, 2015 at 8:37 AM, Stefan Eissing
>  wrote:
>> Any advice on how to add a test host (e.g. real port) to our test suite in 
>> the most compatible way?
> 
> 1426878 added an SSL vhost. It seems like there is a magic port
> assignment the config-generator and client share info about .

Not sure if I'm too late with this, but just add something like the
below - this will add the required Listen and VirtualHost directives to
the generated config files (with an auto-assigned port number).

Kaspar

--- t/conf/ssl/ssl.conf.in  (revision 1709127)
+++ t/conf/ssl/ssl.conf.in  (working copy)
@@ -252,4 +252,10 @@
  SSLCipherSuite AES256-SHA
 

+
+SSLEngine On
+
+# ...
+
+
 

Re: http2 tests

[Stefan Eissing]

Thanks! Yes, I have sth like this in the works in order to test more specific 
http2 edge cases. You'll probably see it sometime next week. 

> Am 17.10.2015 um 10:58 schrieb Kaspar Brand :
> 
>> On 14.10.2015 14:55, Eric Covener wrote:
>> On Wed, Oct 14, 2015 at 8:37 AM, Stefan Eissing
>>  wrote:
>>> Any advice on how to add a test host (e.g. real port) to our test suite in 
>>> the most compatible way?
>> 
>> 1426878 added an SSL vhost. It seems like there is a magic port
>> assignment the config-generator and client share info about .
> 
> Not sure if I'm too late with this, but just add something like the
> below - this will add the required Listen and VirtualHost directives to
> the generated config files (with an auto-assigned port number).
> 
> Kaspar
> 
> --- t/conf/ssl/ssl.conf.in  (revision 1709127)
> +++ t/conf/ssl/ssl.conf.in  (working copy)
> @@ -252,4 +252,10 @@
>  SSLCipherSuite AES256-SHA
> 
> 
> +
> +SSLEngine On
> +
> +# ...
> +
> +
> 
> 
> 

Re: http2 tests

[Rainer Jung]

Am 14.10.2015 um 14:37 schrieb Stefan Eissing:

Need some advice on how to expand our test framework. We had the problem that 
current test on 421 return codes failed as the current setup makes that depend 
on vhosts/other config interference. Undesirable.

Also, I am adding more RFC 7540 compliant behaviour which means mod_http2 will 
check TLS protocol and ciphers. For this I think mod_http2 needs its own host 
as I do not want to mess with SSL test setups that need to perform in various 
environments.

Any advice on how to add a test host (e.g. real port) to our test suite in the 
most compatible way?


Not answering to your question but related to the thread subject: I 
noticed that the h2 tests do not run in a fixed order. That makes it a 
bit harder to compare test results, because the id of a failed test 
might change. Any idea why the order can change? I had a quick look, but 
didn't find a simple reason.


Regards,

Rainer

http2 tests

[Stefan Eissing]

Need some advice on how to expand our test framework. We had the problem that 
current test on 421 return codes failed as the current setup makes that depend 
on vhosts/other config interference. Undesirable.

Also, I am adding more RFC 7540 compliant behaviour which means mod_http2 will 
check TLS protocol and ciphers. For this I think mod_http2 needs its own host 
as I do not want to mess with SSL test setups that need to perform in various 
environments.

Any advice on how to add a test host (e.g. real port) to our test suite in the 
most compatible way? 

Thanks!

//Stefan

Re: http2 tests

[Eric Covener]

On Wed, Oct 14, 2015 at 8:37 AM, Stefan Eissing
 wrote:
> Any advice on how to add a test host (e.g. real port) to our test suite in 
> the most compatible way?

1426878 added an SSL vhost. It seems like there is a magic port
assignment the config-generator and client share info about .