I am posting a soap request using LWP or SOAP::Lite where the access is protected by basic authentication, the soapserver string is using ssl as URL like : https://IP:PORT/path-to-soap-provider.

Without the path-to-soap-provider, just connectiong to IP:PORT, the server replies http requests as well as https.( for any reasson )

The script fails with Error:

SSL connect attempt failed error:14077102:SSL routines:SSL23_GET_SERVE
+R_HELLO:unsupported protocol
[download]

which is fair enough due to the fact server:port does not behave as ssl server if not forced to do

Using openssl s_client to test the connection:

openssl s_client -connect IP:PORT
[download]

fails with the same error message , while:

openssl s_client -connect IP:PORT  -ssl3
[download]

does make the server to act as ssl server

Reducing a script to the basic connection, I can see the same error Message:

 
#!/usr/bin/perl
use IO::Socket::SSL qw(debug3);

my $client = IO::Socket::SSL->new(
        PeerAddr => 'IP',
        PeerPort => 'PORT'    
        SSL_verify_mode => 0x00
);
        ##SSL_version => 'SSLv3'

if(defined $client){ 
        
        print <$client>;
        close $client;
}else{
        warn "I encountered a problem: ",IO::Socket::SSL::errstr();
}
exit;
[download]

The SSL_version config is testing the connection to match the given protocol, but obviously not forcing the server the way openssl does. Any other tests dealing with cookies, authentication, ssl_verfiy_mode or ssl_version , do not help, because obviously the basic connection fails before.

soapui java-Application as well as simple vbs script is doing the job , assuming it is possible in general.

What did I miss ? Is there any way to get the same behaviour as with openssl s_client ?