Skip Menu |

This queue is for tickets about the LWP-Protocol-https CPAN distribution.

Report information
The Basics
Id: 122296
Status: open
Priority: 0/
Queue: LWP-Protocol-https

People
Owner: Nobody in particular
Requestors: 'spro^^*%*^6ut# [...] &$%*c
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 6.07
Fixed in: 6.07



Subject: Test fails under Mac OS X Lion
LWP::Protocol::https version 6.07. https_proxy.t complains with this message: unexpected response: 500 SSL upgrade failed: Client side SNI not supported for this openssl Content-Type: text/plain Client-Date: Fri, 30 Jun 2017 21:36:08 GMT Client-Warning: Internal response SSL upgrade failed: Client side SNI not supported for this openssl at /Library/Perl/5.24.0/LWP/Protocol/http.pm line 205. So, in case the openssl version is involved, here it is: $ openssl version OpenSSL 0.9.8r 8 Feb 2011 Full test script output: $ perl5.24.0 -Mblib t/https_proxy.t 1..56 ok 1 - noproxy http://127.0.0.1:51099/foo -> A.1@nossl ok 2 - URL in request -> /foo ok 3 - noproxy http://127.0.0.1:51099/bar -> A.2@nossl ok 4 - URL in request -> /bar ok 5 - noproxy http://127.0.0.1:51100/foo -> B.1@nossl ok 6 - URL in request -> /foo ok 7 - noproxy http://127.0.0.1:51100/bar -> B.2@nossl ok 8 - URL in request -> /bar ok 9 - noproxy http://127.0.0.1:51099/tor -> A.3@nossl ok 10 - URL in request -> /tor ok 11 - noproxy http://127.0.0.1:51100/tor -> B.3@nossl ok 12 - URL in request -> /tor ok 13 - proxy http://foo/foo -> C.1.auth@nossl ok 14 - URL in request -> http://foo/foo ok 15 - proxy http://foo/bar -> C.2.auth@nossl ok 16 - URL in request -> http://foo/bar ok 17 - proxy http://bar/foo -> C.3.auth@nossl ok 18 - URL in request -> http://bar/foo ok 19 - proxy http://bar/bar -> C.4.auth@nossl ok 20 - URL in request -> http://bar/bar ok 21 - proxy http://foo/tor -> C.5.auth@nossl ok 22 - URL in request -> http://foo/tor ok 23 - proxy http://bar/tor -> C.6.auth@nossl ok 24 - URL in request -> http://bar/tor # creating cert for direct.ssl.access ok 25 - noproxy https://127.0.0.1:51099/foo -> D.1@direct.ssl.access ok 26 - URL in request -> /foo ok 27 - noproxy https://127.0.0.1:51099/bar -> D.2@direct.ssl.access ok 28 - URL in request -> /bar # creating cert for direct.ssl.access ok 29 - noproxy https://127.0.0.1:51100/foo -> E.1@direct.ssl.access ok 30 - URL in request -> /foo ok 31 - noproxy https://127.0.0.1:51100/bar -> E.2@direct.ssl.access ok 32 - URL in request -> /bar ok 33 - noproxy https://127.0.0.1:51099/tor -> D.3@direct.ssl.access ok 34 - URL in request -> /tor ok 35 - noproxy https://127.0.0.1:51100/tor -> E.3@direct.ssl.access ok 36 - URL in request -> /tor # creating cert for foo unexpected response: 500 SSL upgrade failed: Client side SNI not supported for this openssl Content-Type: text/plain Client-Date: Fri, 30 Jun 2017 21:36:08 GMT Client-Warning: Internal response SSL upgrade failed: Client side SNI not supported for this openssl at /Library/Perl/5.24.0/LWP/Protocol/http.pm line 205. # Looks like you planned 56 tests but ran 36. # Looks like your test exited with 25 just after 36. I really have no idea what this message means. What can I do to help debug it?
I've the same issue on Linux 3.0.101-68-xen SMP Tue Dec 1 16:21:37 UTC 2015 (ed01a9f) x86_64 x86_64 x86_64 GNU/Linux and OpenSSL 0.9.8j-fips 07 Jan 2009 On Fri Jun 30 17:40:33 2017, SPROUT wrote: Show quoted text
> LWP::Protocol::https version 6.07. > > https_proxy.t complains with this message: > > unexpected response: 500 SSL upgrade failed: Client side SNI not > supported for this openssl > Content-Type: text/plain > Client-Date: Fri, 30 Jun 2017 21:36:08 GMT > Client-Warning: Internal response > > SSL upgrade failed: Client side SNI not supported for this openssl at > /Library/Perl/5.24.0/LWP/Protocol/http.pm line 205. > > So, in case the openssl version is involved, here it is: > > $ openssl version > OpenSSL 0.9.8r 8 Feb 2011 > > Full test script output: > > $ perl5.24.0 -Mblib t/https_proxy.t > 1..56 > ok 1 - noproxy http://127.0.0.1:51099/foo -> A.1@nossl > ok 2 - URL in request -> /foo > ok 3 - noproxy http://127.0.0.1:51099/bar -> A.2@nossl > ok 4 - URL in request -> /bar > ok 5 - noproxy http://127.0.0.1:51100/foo -> B.1@nossl > ok 6 - URL in request -> /foo > ok 7 - noproxy http://127.0.0.1:51100/bar -> B.2@nossl > ok 8 - URL in request -> /bar > ok 9 - noproxy http://127.0.0.1:51099/tor -> A.3@nossl > ok 10 - URL in request -> /tor > ok 11 - noproxy http://127.0.0.1:51100/tor -> B.3@nossl > ok 12 - URL in request -> /tor > ok 13 - proxy http://foo/foo -> C.1.auth@nossl > ok 14 - URL in request -> http://foo/foo > ok 15 - proxy http://foo/bar -> C.2.auth@nossl > ok 16 - URL in request -> http://foo/bar > ok 17 - proxy http://bar/foo -> C.3.auth@nossl > ok 18 - URL in request -> http://bar/foo > ok 19 - proxy http://bar/bar -> C.4.auth@nossl > ok 20 - URL in request -> http://bar/bar > ok 21 - proxy http://foo/tor -> C.5.auth@nossl > ok 22 - URL in request -> http://foo/tor > ok 23 - proxy http://bar/tor -> C.6.auth@nossl > ok 24 - URL in request -> http://bar/tor > # creating cert for direct.ssl.access > ok 25 - noproxy https://127.0.0.1:51099/foo -> D.1@direct.ssl.access > ok 26 - URL in request -> /foo > ok 27 - noproxy https://127.0.0.1:51099/bar -> D.2@direct.ssl.access > ok 28 - URL in request -> /bar > # creating cert for direct.ssl.access > ok 29 - noproxy https://127.0.0.1:51100/foo -> E.1@direct.ssl.access > ok 30 - URL in request -> /foo > ok 31 - noproxy https://127.0.0.1:51100/bar -> E.2@direct.ssl.access > ok 32 - URL in request -> /bar > ok 33 - noproxy https://127.0.0.1:51099/tor -> D.3@direct.ssl.access > ok 34 - URL in request -> /tor > ok 35 - noproxy https://127.0.0.1:51100/tor -> E.3@direct.ssl.access > ok 36 - URL in request -> /tor > # creating cert for foo > unexpected response: 500 SSL upgrade failed: Client side SNI not > supported for this openssl > Content-Type: text/plain > Client-Date: Fri, 30 Jun 2017 21:36:08 GMT > Client-Warning: Internal response > > SSL upgrade failed: Client side SNI not supported for this openssl at > /Library/Perl/5.24.0/LWP/Protocol/http.pm line 205. > # Looks like you planned 56 tests but ran 36. > # Looks like your test exited with 25 just after 36. > > I really have no idea what this message means. What can I do to help > debug it?