Thanks a lot!
> Am 22.10.2018 um 14:06 schrieb Rainer Jung :
>
> This seems to work nicely, committed in r1844546. Tests with old OpenSSL
> either in client or server result in TLSv1 and disable h2 tests. TLS test
> requests that result in TLSv1_2 or TLSv1_3 enable h2 tests.
>
> Regards,
>
>
This seems to work nicely, committed in r1844546. Tests with old OpenSSL
either in client or server result in TLSv1 and disable h2 tests. TLS
test requests that result in TLSv1_2 or TLSv1_3 enable h2 tests.
Regards,
Rainer
Am 22.10.2018 um 12:37 schrieb Rainer Jung:
I wonder whether it would
I wonder whether it would be easier to check whether a TLS connection
uses TLS 1.2 or later and disable the h2 test if not.
Nevertheless the module for checking the server version might be useful,
but here I guess checking the TLS version is more appropriate.
But that might mean, that the tes
On 10/21/2018 6:46 AM, Rainer Jung wrote:
> Am 18.10.2018 um 14:23 schrieb Stefan Eissing:
>>> Am 18.10.2018 um 14:12 schrieb Rainer Jung :
>>>
>>> - t/modules/http2.t fails when the server is build using OpenSSL
>>> 0.9.8zh with the "Bad plan. You planned 52 tests..." message
>>> indicating, th
Am 18.10.2018 um 14:23 schrieb Stefan Eissing:
Am 18.10.2018 um 14:12 schrieb Rainer Jung :
- t/modules/http2.t fails when the server is build using OpenSSL 0.9.8zh with the
"Bad plan. You planned 52 tests..." message indicating, that h2 using TLS does
not work. It happens on all platforms, b