title: How can I force TLS1.2 on the SOAP proxy?
body: <p>Because of BEAST, CRIME, and similar SSL attacks, we've been tightening our IIS encryption parameters. At this point, very old web apps that use ASMX web services suddenly stopped responding over SSL. The error message was</p>
  
  <pre><code>Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
  </code></pre>
  
  <p>We isolated the problem to the server side of the connection, not the client side, because SoapUI also showed a connection problem.</p>
  
  <p>We further isolated the problem to the guts of the SOAP implementation, because plain ASPX pages worked in the browser.</p>
  
  <p>Rolling back the recent anti-BEAST changes made the problem go away.</p>
  
  <p>So the question becomes: what do we have to do in our .NET code to make it use TLS 1.2 to connect to the server, rather than TLS 1.0 or any earlier protocol?</p>