When using Connector::Proxy::HTTP using a https URI the Connector implementation consumes the role Connector::Role::SSLUserAgent which sets several additional settings for the underlying TLS class.
None of the options are error-checked, if e. g. a file does not exist, Connector will accept the configuration, and the underlying TLS implementation bails out with a very generic error 500.
Without error logging and sanity checking it is not possible to determine the actual cause of the problem.
When using Connector::Proxy::HTTP using a https URI the Connector implementation consumes the role Connector::Role::SSLUserAgent which sets several additional settings for the underlying TLS class.
None of the options are error-checked, if e. g. a file does not exist, Connector will accept the configuration, and the underlying TLS implementation bails out with a very generic error 500.
Without error logging and sanity checking it is not possible to determine the actual cause of the problem.