title: 500 SSL negotiation failed
body: <p>I have a new-onset problem on my Windows XP Pro system, demonstrated by the Perl code below (which is, of course, a very cut down example from a much larger program).</p>
  
  <p>It used to work until a few days ago, and I'm pulling my hair out trying to figure out what might have changed on the system to stop it working, and I'm hoping someone here might be able to give me some clues.  (It still works fine on my Windows 8.1 system.)</p>
  
  <p>The issue is that the code below (now) fails with "500 SSL negotiation failed".</p>
  
  <pre><code>use strict;
  use warnings;
  
  use HTTP::Request;
  use LWP::UserAgent;
  
  $ENV{HTTPS_DEBUG} = 1;
  
  my $url = "https://secure.quksdns4.net:2087/";
  my $ua  = LWP::UserAgent-&gt;new;
  my $req = HTTP::Request-&gt;new (GET =&gt; $url);
  my $res = $ua-&gt;request($req);
  my $sts = $res-&gt;code;
  my $hdr = $res-&gt;headers_as_string;
  my $txt = $res-&gt;content;
  
  print "\n".$sts."\n\n".$hdr."\n";
  print $txt if ($sts == 500);
  
  exit;
  </code></pre>
  
  <p>The output is:</p>
  
  <pre><code>SSL_connect:before/connect initialization
  SSL_connect:SSLv2/v3 write client hello A
  SSL_connect:error in SSLv2/v3 read server hello A
  SSL_connect:before/connect initialization
  SSL_connect:SSLv3 write client hello A
  SSL3 alert read:fatal:handshake failure
  SSL_connect:failed in SSLv3 read server hello A
  SSL_connect:before/connect initialization
  SSL_connect:SSLv2 write client hello A
  SSL_connect:error in SSLv2 read server hello A
  
  500
  
  Content-Type: text/plain
  Client-Date: Sat, 25 Oct 2014 14:52:43 GMT
  Client-Warning: Internal response
  
  500 SSL negotiation failed:
  </code></pre>
  
  <p>Curiously however it works (albeit not very usefully!) if the port number (:2087) is removed.</p>
  
  <p>Active Perl v5.8.8 (which I haven't changed in years), ssleay32 &amp; libeay32 dlls are 0.9.8.1 (also unchanged in years), and while there's a few on the system those in C:\Perl\bin are the only ones in the path.</p>
  
  <p>Any hints as to what might have changed to stop the above working gratefully received!</p>