IO-Socket-SSL
view release on metacpan or search on metacpan
lib/IO/Socket/SSL.pm view on Meta::CPAN
if ($ssl_ver
&& ($content_type != $trace_constants{SSL3_RT_HEADER})
&& ($content_type != $trace_constants{SSL3_RT_INNER_CONTENT_TYPE})
) {
# the info given when the version is zero is not that useful for us
$ssl_ver >>= 8; # check the upper 8 bits only below */
# SSLv2 doesn't seem to have TLS record-type headers, so OpenSSL
# always pass-up content-type as 0. But the interesting message-type
# is at 'buf[0]'.
my $tls_rt_name = ($ssl_ver == $trace_constants{SSL3_VERSION_MAJOR} && $content_type)
? $tc_type2s{$content_type} || "TLS Unknown (type=$content_type)"
: "";
my $msg_type;
my $msg_name;
if ($content_type == $trace_constants{SSL3_RT_CHANGE_CIPHER_SPEC}) {
$msg_type = unpack('c1', $buf);
lib/IO/Socket/SSL.pod view on Meta::CPAN
occurred the method will return C<''>.
=item soft_error
This returns the soft error(s) which occurred when asking the OCSP responders.
=item requests
This will return a hash consisting of C<(url,request)>-tuples, e.g. which
contain the OCSP request string and the URL where it should be sent too. The
usual way to send such a request is as HTTP POST request with a content-type
of C<application/ocsp-request> or as a GET request with the base64 and
url-encoded request is added to the path of the URL.
After you've handled all these requests and added the response with
C<add_response> you should better call this method again to make sure, that no
more requests are outstanding. IO::Socket::SSL will combine multiple OCSP
requests for the same server inside a single request, but some server don't
give a response to all these requests, so that one has to ask again with the
remaining requests.
( run in 1.564 second using v1.01-cache-2.11-cpan-524268b4103 )