Hello folks,
I'm trying to update my OpenBSD smoker and found out that one of the
tests from POE::Component::Client::HTTP is broken:
runner@f27d9f8d74b9:~/.cpan/build/RCAPUTO-0/POE-Component-Client-HTTP-0.949$
prove -l -v -m t/01_ssl.t
t/01_ssl.t ..
1..1
not ok 1 - Got OK response
# Failed test 'Got OK response'
# at t/01_ssl.t line 62.
# got: '400'
# expected: '200'
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
Test Summary Report
-------------------
t/01_ssl.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Files=1, Tests=1, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.44 cusr
0.09 csys = 0.56 CPU)
Result: FAIL
Taking a look at the code, the original website for testing the TLS
connections has an invalid certificate:
$ curl -v https://thirdlobe.com
* Rebuilt URL to: https://thirdlobe.com/
* Trying 66.228.57.90...
* TCP_NODELAY set
* Connected to thirdlobe.com (66.228.57.90) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.0 (IN), TLS handshake, Certificate (11):
* TLSv1.0 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: self signed certificate
* stopped the pause stream!
* Closing connection 0
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Changing the website to https://www.google.com/ (the ending slash is
required to avoid HTTP 301) worked as expected:
$ prove -l -v -m t/01_ssl.t
t/01_ssl.t ..
1..1
# Trying to connect to https://www.google.com/ with TLS...
ok 1 - Got OK response
ok
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.35 cusr
0.09 csys = 0.46 CPU)
Result: PASS
I added Test::More::note to the test to print the new HTTPS target.
I was moving to open a ticket to POE::Component::Client::HTTP and it
seems to me that the module is not being maintained anymore: long time
opened issues at RT and pull requests waiting to be applied within Github.
It seems to me that the whole POE (and related modules) are not being
maintained anymore... am I right?
Thanks,
Alceu