Thanks Khen1950fx
Apparently LWP::Protocol::HTTPS has not been installed on my system, and unfortunately it failed the install tests
Running make test
C:\strawberry\perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_h
+arness(0, 'blib\lib', 'blib\arch')" t/*.t
t/apache.t .. 1/4
# Failed test at t/apache.t line 15.
# Failed test at t/apache.t line 16.
# 'write failed: at C:/strawberry/perl/site/lib/LWP
+/Protocol/http.pm line 238.
# '
# doesn't match '(?^:Apache Software Foundation)'
# Failed test at t/apache.t line 23.
# Looks like you failed 3 tests of 4.
t/apache.t .. Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/4 subtests
So now I am working to figure out how to get this module to install. There is no issue connecting to https://apache.org/ in my browsers.
Using my internal https host, the script continues on to report:
[...]
DEBUG: .../IO/Socket/SSL.pm:537: Net::SSLeay::connect -> -1
DEBUG: .../IO/Socket/SSL.pm:543: fatal SSL error: SSL connect attempt
+failed with unknown error
[...]
However if I change the host to apache.org (443):
DEBUG: .../IO/Socket/SSL.pm:1784: new ctx 60344912
OK: Connected
DEBUG: .../IO/Socket/SSL.pm:1821: free ctx 60344912 open=60344912
DEBUG: .../IO/Socket/SSL.pm:1829: OK free ctx 60344912
not ok: at [ the $socket->close line ]
There's one other important detail that I left out. The server that I'm connecting to is a load balancer. I don't think this should matter as it is supposed transparently forward the requests/responses.
I'm going continue to explore testing against a known, working, external web service to determine if our internal web service/load balancer are breaking the script. |