Re: [libmicrohttpd] HTTPS errors

[Evgeny Grin]

Tested on CentOS 6.9 with current updates.
MHD 0.9.55, GnuTLS 2.12.23 (from distribution repo).
No test fails.

-- 
Best Wishes,
Evgeny Grin

On 16.08.2017 14:57, Evgeny Grin wrote:
> Looks like you are using outdated and unsupported version of RHEL.
> Actual version in RHEL 6 is 6.9. Version 6.8 currently in Extended support.
> Most probably it is caused by outdated GnuTLS version. 2.x versions are
> known to have problems.
> However I'll try to reproduce it on CentOS when I'll have some spare time.
> 
> -- Best Wishes, Evgeny Grin On 16.08.2017 12:03, Štefan Bellus wrote:
>> Hi
>>
>> I run test compiled with autotools and get SAME (return value 77 in your
>> driver means skip and in cmake it means fail) result.
>> MHD version 0.9.55
>> GnuTLS version 2.8.5
>> OS type and version RedHat 6.4 (uname -a -> Linux buildvm
>> 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64
>> x86_64 GNU/Linux)
>>

>> ============================================================================
>> Making check in https
>> Making check in .
>> SKIP: test_tls_options
>> PASS: test_https_multi_daemon
>> PASS: test_https_get
>> FAIL: test_https_get_select
>> PASS: test_https_get_parallel
>> SKIP: test_https_get_parallel_threads
>> SKIP: test_https_session_info
>> PASS: test_https_time_out
>> PASS: test_tls_authentication
>> PASS: test_empty_response
>> ============================================================================
>> Testsuite summary for GNU Libmicrohttpd 0.9.55
>> ============================================================================
>> # TOTAL: 10
>> # PASS:  6
>> # SKIP:  3
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>> ============================================================================
>> See src/testcurl/https/test-suite.log
>> Please report to address@hidden <mailto:address@hidden>
>> ============================================================================
>>
>> Best regards
>> Stevo
>>
>> On Tue, Aug 15, 2017 at 11:14 PM, Evgeny Grin <address@hidden
>> <mailto:address@hidden>> wrote:
>>
>>     All tests are passed on GNU/Linux (i686, x86_64, SPARC, ARM), macOS,
>>     Windows (MinGW and MSVC), FreeBSD, OpenBSD, NetBSD, Solaris.
>>     One or two tests are failing on GNU Hurd.
>>
>>     If you are using git:
>>     autoreconf -v
>>     /configure
>>     make all
>>     make check
>>
>>     If you are using released tarball, skip first step.
>>
>>     --
>>     Best Wishes,
>>     Evgeny Grin
>>
>>     On 15.08.2017 22:55, Štefan Bellus wrote:
>>     > Ok.
>>     >
>>     > If it is working on your pc then I will provide for you the requested 
>> info.
>>     >
>>     > When I build with autotools then NO tests are built.
>>     >
>>     > Please could you give me some hint how to build them?
>>     >
>>     >
>>     > Typed with thumbs.
>>     >
>>     > On Aug 15, 2017 20:52, "Evgeny Grin" <address@hidden 
>> <mailto:address@hidden>
>>     > <mailto:address@hidden <mailto:address@hidden>>> wrote:
>>     >
>>     >     Hi Štefan,
>>     >
>>     >     Could you provide more details?
>>     >     MHD version, GnuTLS version, OS type and version, text output
>>     of failed
>>     >     tests?
>>     >
>>     >     Of course it is not OK, HTTPS should works fine.
>>     >
>>     >     --
>>     >     Best Wishes,
>>     >     Evgeny Grin
>>     >
>>     >     On 15.08.2017 19:42, Štefan Bellus wrote:
>>     >     > Hi
>>     >     >
>>     >     > I tune configuration and add test, examples target. I have
>>     following
>>     >     > test results.
>>     >     > The following tests FAILED:
>>     >     >          39 - tls_options (Failed)
>>     >     >          43 - https_get_select (Failed)
>>     >     >          44 - https_session_info (Failed)
>>     >     > Also I have trouble when I start src/examples/demo_https (it
>>     is build
>>     >     > with autotools). The server reports "Error: received
>>     handshake message
>>     >     > out of context" and chrome reports ERR_EMPTY_RESPONSE.
>>     >     >
>>     >     > Is it OK or I should investigate more?
>>     >
>>
>>

signature.asc
Description: OpenPGP digital signature